From: Joe Conway <joseph.conway@home.com>
To: Peter Eisentraut <peter_e@gmx.net>
Cc: pgsql-docs@postgresql.org
Subject: Bytea docs (was Re: [PATCHES] bytea datatype documentation patch)
Date: Tue, 20 Nov 2001 14:26:02 -0800
Message-ID: <3BFAD87A.7090605@home.com> (raw)
References: <Pine.LNX.4.30.0111201526530.613-100000@peter.localdomain>
[ redirected from patches to pgsql-docs ]
Peter Eisentraut wrote:
> I feel that basing the whole discussion on what "ASCII" characters can be
> stored, are nonprintable, must be escaped, etc. is not appropriate.
> Bytea doesn't store characters, it stores bytes (or octets, as you wish).
> The correspondence between bytes and characters is old-fashioned and
> pretty much does not exist in SQL except for a few places such as
> OCTET_LENGTH.
>
> Conversely, the discussion about whether text should be able to cope with
> zero bytes is nonsensical because text stores characters and not bytes.
>
> So I would base this discussion on the premise "bytea stores binary data"
> (insert examples).
Thanks for the input, Peter.
I was struggling to come up with a better way to say, for example "ASCII
value XX", that would be clear to the reader. Do you think referring to
"bytes of decimal value XX" is better?
I'll take another stab at this with your guidance in mind.
>
> Some stylistic issues:
>
> bytea => <type>bytea</type>
>
> NULLs => zero bytes/bytes of value zero ("NULL" is too overloaded)
>
> 'non-printable' => <quote>nonprintable</quote>
>
> MUST => <emphasis>must</emphasis>
>
Good input -- I'll fix these too.
Thanks!
-- Joe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: joseph.conway@home.com, peter_e@gmx.net
Subject: Re: Bytea docs (was Re: [PATCHES] bytea datatype documentation patch)
In-Reply-To: <3BFAD87A.7090605@home.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox