| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | bugs-postgresql(at)antipoul(dot)fr, pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Mention invalid null byte sequence |
| Date: | 2020-12-07 09:02:43 |
| Message-ID: | 0f0470f6d8c543793d2b71913cb230daea1aef3a.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Sat, 2020-12-05 at 21:58 +0000, PG Doc comments form wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/13/datatype-character.html
> Description:
>
> I discovered accidentally that PostgreSQL doesn't accept null byte in text
> type. It seems that Oracle does (see
> https://www.postgresql.org/message-id/de752e01-f36c-821e-9181-cfba78c0fbc8%40propaas.com)
> and SQLite does it too.
>
> So it should written in the character type that null byte are not accepted,
> it would make like easier to migrate to PostgreSQL :)
+1; how about the attached patch?
Yours,
Laurenz Albe
| Attachment | Content-Type | Size |
|---|---|---|
| Document-that-NUL-characters-are-not-supported.patch | text/x-patch | 600 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrien CLERC | 2020-12-07 09:57:47 | Re: Mention invalid null byte sequence |
| Previous Message | PG Doc comments form | 2020-12-05 21:58:49 | Mention invalid null byte sequence |