Support for \u0000?

From: Matthew Byrne <mjw(dot)byrne(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Support for \u0000?
Date: 2017-07-15 13:49:16
Message-ID: CAE37PpOn=McGeokmny4tm4FTHmXSG4KydgUJemKqT9XxkrrTmg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Are there any plans to support \u0000 in JSONB and, relatedly, UTF code
point 0 in TEXT? To the best of my knowledge \u0000 is valid in JSON and
code point 0 is valid in UTF-8 but Postgres rejects both, which severely
limits its usefulness in many cases.

I am currently working around the issue by using the JSON type, which
allows \u0000 to be stored, but this is far from ideal because it can't be
cast to TEXT or JSONB and can't even be accessed:

mydb=# select '{"thing":"\u0000"}'::json->>'thing';
ERROR: unsupported Unicode escape sequence
DETAIL: \u0000 cannot be converted to text.
CONTEXT: JSON data, line 1: {"thing":...

Regards,

Matt

Responses

Browse pgsql-general by date

  From Date Subject
Next Message dilaz03 . 2017-07-15 13:56:32 Planner statistics usage for composite type
Previous Message Clodoaldo Neto 2017-07-15 11:38:46 Failed DNF dependency in Fedora