Re: Mention invalid null byte sequence

Поиск
Список
Период
Сортировка
От Laurenz Albe
Тема Re: Mention invalid null byte sequence
Дата
Msg-id 48125106de1a275b1e0c2d46b7c0a56a2b0675cb.camel@cybertec.at
обсуждение исходный текст
Ответ на Re: Mention invalid null byte sequence  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: Mention invalid null byte sequence  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-docs
On Mon, 2020-12-07 at 15:27 -0500, Tom Lane wrote:
> Laurenz Albe <laurenz.albe@cybertec.at> writes:
> > 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:
> > > 
> > > 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?
> 
> I had thought that this was already documented, but after digging around
> I can only find it mentioned in the contexts of saying that literal
> strings and quoted identifiers can't contain \0.  So yeah, we need to
> improve that.
> 
> I agree with the submitter that the place one would expect to read about
> this is in datatype-character.html.  So I'd propose the attached.
> Maybe there's reason to repeat the info in charset.sgml, but it seems
> like more of a datatype limitation than a character set issue.

+1 on your patch.

Yours,
Laurenz Albe




В списке pgsql-docs по дате отправления:

Предыдущее
От: PG Doc comments form
Дата:
Сообщение: Wrong configuration of tcp_user_timeout can terribly affects tcp_keepalives mechanism
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Mention invalid null byte sequence