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 [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073
