RE: JDBC 'Unterminated quoted string'
От | Peter Mount |
---|---|
Тема | RE: JDBC 'Unterminated quoted string' |
Дата | |
Msg-id | 1B3D5E532D18D311861A00600865478CF1B52A@exchange1.nt.maidstone.gov.uk обсуждение исходный текст |
Ответ на | JDBC 'Unterminated quoted string' (Christopher Farley <chris@northernbrewer.com>) |
Список | pgsql-interfaces |
If it's going to break that many interfaces, then it's not going to be worth the hassle. Peter -- Peter Mount Enterprise Support Officer, Maidstone Borough Council Email: petermount@maidstone.gov.uk WWW: http://www.maidstone.gov.uk All views expressed within this email are not the views of Maidstone Borough Council -----Original Message----- From: Tom Lane [mailto:tgl@sss.pgh.pa.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@ucs.co.za> writes: > In brief, there seems to be some problem at the backend inserting a > \0. 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 по дате отправления: