Re: Patch for DBD::Pg pg_relcheck problem

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: David Wheeler <david(at)wheeler(dot)net>
Cc: Ian Barwick <barwick(at)gmx(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, dbi-dev(at)perl(dot)org, pgsql-interfaces(at)postgresql(dot)org
Subject: Re: Patch for DBD::Pg pg_relcheck problem
Date: 2002-12-15 02:35:07
Message-ID: 200212150235.gBF2Z7923625@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-interfaces

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(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Brown 2002-12-15 06:02:47 Re: [HACKERS] PostgreSQL Global Development Group
Previous Message David Wheeler 2002-12-15 01:58:17 Re: Patch for DBD::Pg pg_relcheck problem

Browse pgsql-interfaces by date

  From Date Subject
Next Message Ian Barwick 2002-12-15 23:36:26 Re: Patch for DBD::Pg pg_relcheck problem
Previous Message David Wheeler 2002-12-15 01:58:17 Re: Patch for DBD::Pg pg_relcheck problem