Skip site navigation (1) Skip section navigation (2)

RE: JDBC 'Unterminated quoted string'

From: Peter Mount <petermount(at)maidstone(dot)gov(dot)uk>
To: "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Interfaces <pgsql-interfaces(at)postgresql(dot)org>
Subject: RE: JDBC 'Unterminated quoted string'
Date: 2000-11-10 14:54:38
Message-ID: 1B3D5E532D18D311861A00600865478CF1B52A@exchange1.nt.maidstone.gov.uk (view raw or flat)
Thread:
Lists: 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(at)maidstone(dot)gov(dot)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(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
> \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 by date

Next:From: Tom LaneDate: 2000-11-10 14:54:43
Subject: Re: JDBC 'Unterminated quoted string'
Previous:From: Francis SolomonDate: 2000-11-10 11:12:20
Subject: RE: Access 2000 and empty fields

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group