From: | Matthew Byrne <mjw(dot)byrne(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Support for \u0000? |
Date: | 2017-07-19 22:36:06 |
Message-ID: | CAE37PpOKCs9aBvOPtMbwJ7UvFYSZWAMia=WOp0U2tNKWgnGE9A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I see. Thanks for the quick responses!
On Wed, Jul 19, 2017 at 11:32 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Matthew Byrne <mjw(dot)byrne(at)gmail(dot)com> writes:
> > Would a more feasible approach be to introduce new types (say, TEXT2 and
> > JSONB2 - or something better-sounding) which are the same as the old ones
> > but add for support \u0000 and UTF 0? This would isolate nul-containing
> > byte arrays to the implementations of those types and keep backward
> > compatibility by leaving TEXT and JSONB alone.
>
> The problem is not inside those datatypes; either text or jsonb could
> trivially store \0 bytes. The problem is passing such values through
> APIs that don't support it. Changing those APIs would affect *all*
> datatypes.
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Alessandro_feliz | 2017-07-19 23:41:56 | Postgres csv logging |
Previous Message | Tom Lane | 2017-07-19 22:32:53 | Re: Support for \u0000? |