If it's going to break that many interfaces, then it's not going to be worth
Enterprise Support Officer, Maidstone Borough Council
All views expressed within this email are not the views of Maidstone Borough
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: Friday, November 10, 2000 2:55 PM
To: Grant Finnemore
Cc: Peter Mount; Interfaces
Subject: Re: [INTERFACES] JDBC 'Unterminated quoted string'
Grant Finnemore <gaf(at)ucs(dot)co(dot)za> writes:
> In brief, there seems to be some problem at the backend inserting a
char(n) does not support embedded nulls. Offhand I believe that bytea
is the only datatype that does, and even then you have to write 'em
with a backslash-escape --- ie, send "\000" not an actual null.
Fixing this is not likely to happen soon, if ever, because it would
involve a massive overhaul of the datatype I/O system, with such
side-effects as breaking every user-defined datatype in existence.
Textual representations of datatypes are C strings --- ie,
null-terminated --- and all datatype I/O routines depend on that.
regards, tom lane
pgsql-interfaces by date
|Next:||From: Tom Lane||Date: 2000-11-10 14:54:43|
|Subject: Re: JDBC 'Unterminated quoted string' |
|Previous:||From: Francis Solomon||Date: 2000-11-10 11:12:20|
|Subject: RE: Access 2000 and empty fields|