From: Bruce Momjian <pgman@candle.pha.pa.us>
To: David Wheeler <david@wheeler.net>
Cc: Ian Barwick <barwick@gmx.net>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: dbi-dev@perl.org
Cc: pgsql-interfaces@postgresql.org
Subject: Re: Patch for DBD::Pg pg_relcheck problem
Date: Sat, 14 Dec 2002 21:35:07 -0500 (EST)
Message-ID: <200212150235.gBF2Z7923625@candle.pha.pa.us> (raw)
In-Reply-To: <ADD3699E-0FD0-11D7-8FFE-0003931A964A@wheeler.net>
David Wheeler wrote:
> Since, however, nulls aren't really allowed in any PostgreSQL data type
> (except bytea, and then only if specifically bound as such to a
> prepared statement), I'm not sure what to do about this. We can't leave
> the data alone unless we just want PostgreSQL to throw an error (likely
> to be a mysterious error, as the user won't know why her data is
> getting truncated).
>
> I think...throw an exception, since PostgreSQL can't handle the null
> byte. Then it will be up to the user to clean up her data, and we won't
> have to touch it.
Yep, throw an error, and maybe point to bytea as the solution, until we
have a better one. ;-)
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
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-interfaces@postgresql.org
Cc: pgman@candle.pha.pa.us, david@wheeler.net, barwick@gmx.net, tgl@sss.pgh.pa.us, dbi-dev@perl.org
Subject: Re: Patch for DBD::Pg pg_relcheck problem
In-Reply-To: <200212150235.gBF2Z7923625@candle.pha.pa.us>
* 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