BUG #8407: json_populate_record case sensitivity

Started by Nonameover 12 years ago3 messagesbugs

george.stragand@gmail.com

over 12 years ago

The following bug has been logged on the website:

Bug reference: 8407
Logged by: Possible bug with json_populate_record?
Email address: george.stragand@gmail.com
PostgreSQL version: 9.3rc1
Operating system: Ubuntu
Description:

Using PostgreSQL 9.3beta2.

SELECT version();

PostgreSQL 9.3beta2 on x86_64-unknown-linux-gnu, compiled by gcc
(Ubuntu/Linaro 4.6.3-1ubuntu5) 4.6.3, 64-bit

The question is regarding json keys in uppercase. Here's a small example:

create type testPop as (
foobar int
);

This returns as expected:

select * from json_populate_record(null::testPop, '{"foobar": 1}');

Whereas this form, upper-cased version of foobar, returns an empty record.

select * from json_populate_record(null::testPop, '{"FOOBAR": 1}');

That could be working as designed, as 'foobar' != 'FOOBAR', and is
completely acceptable.

So, drop the type and recreate it with these statements:

drop type testPop;

create type testPop as (
FOOBAR int
);

And this form will still return an empty record:

select * from json_populate_record(null::testPop, '{"FOOBAR": 1}');

Again, this could be 100% working as designed per the contract of column
names. That's acceptable, but then the question is how to match keys
expressed as uppercase. The source of the json is from an external vendor,
so not something we can go back and change directly.

Thank you.

--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

Alvaro Herrera

alvherre@2ndquadrant.com

over 12 years ago

In reply to: Noname (#1)

Re: BUG #8407: json_populate_record case sensitivity

george.stragand@gmail.com escribiï¿½:

create type testPop as (
FOOBAR int
);

Your problem is that this identifier has been downcased. This works:

alvherre=# create type testPop as (
alvherre(# "FOOBAR" int);
CREATE TYPE
alvherre=# select * from json_populate_record(null::testPop, '{"FOOBAR": 1}');
FOOBAR
--------
1
(1 fila)

--
ï¿½lvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

Andres Freund

andres@anarazel.de

over 12 years ago

In reply to: Noname (#1)

Re: BUG #8407: json_populate_record case sensitivity

On 2013-08-29 21:08:56 +0000, george.stragand@gmail.com wrote:

The following bug has been logged on the website:

Bug reference: 8407
Logged by: Possible bug with json_populate_record?
Email address: george.stragand@gmail.com
PostgreSQL version: 9.3rc1
Operating system: Ubuntu
Description:

Using PostgreSQL 9.3beta2.

SELECT version();

PostgreSQL 9.3beta2 on x86_64-unknown-linux-gnu, compiled by gcc
(Ubuntu/Linaro 4.6.3-1ubuntu5) 4.6.3, 64-bit

The question is regarding json keys in uppercase. Here's a small example:

create type testPop as (
foobar int
);

This returns as expected:

select * from json_populate_record(null::testPop, '{"foobar": 1}');

Whereas this form, upper-cased version of foobar, returns an empty record.

select * from json_populate_record(null::testPop, '{"FOOBAR": 1}');

That could be working as designed, as 'foobar' != 'FOOBAR', and is
completely acceptable.

So, drop the type and recreate it with these statements:

drop type testPop;

create type testPop as (
FOOBAR int
);

Postgresql lowercases unquoted identifiers. Make that »"FOOBAR" int« and
it should work.

Greetings,

Andres Freund

--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs