Re: Mention invalid null byte sequence
Adrien CLERC <bugs-postgresql@antipoul.fr>
From: Adrien CLERC <bugs-postgresql@antipoul.fr>
To: Laurenz Albe <laurenz.albe@cybertec.at>, pgsql-docs@lists.postgresql.org
Date: 2020-12-07T09:57:47Z
Lists: pgsql-docs
Le 07/12/2020 à 10:02, Laurenz Albe a écrit : > 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? That would be a good start indeed. I don't know the policy for documentation redundancy in PostgreSQL, but it should be good to mention that also in https://www.postgresql.org/docs/current/sql-syntax-lexical.html#SQL-SYNTAX-STRINGS-ESCAPE since the basic "SELECT E'la\x00la';" will fail while "SELECT E'la\x01la';" will not. And, as a lazy person, I also would like to see it in the general datatype page, since it's a common behavior. Anyway, merging the first patch will enable the search for "NUL character" to return a result, and that will be definitively a nice improvement! Have a nice day! Adrien
Commits
-
Doc: explain that the string types can't store \0 (ASCII NUL).
- c5ba66077054 13.2 landed
- b4a5d5406594 10.16 landed
- 9a2641911aea 14.0 landed
- 3410a9b57062 9.6.21 landed
- 10c601578a25 11.11 landed
- 101c8ae02cc0 12.6 landed
- 0921b86ca1e4 9.5.25 landed