From: Tom Lane <tgl@sss.pgh.pa.us>
To: Grant Finnemore <gaf@ucs.co.za>
Cc: Peter Mount <petermount@maidstone.gov.uk>
Cc: Interfaces <pgsql-interfaces@postgresql.org>
Subject: Re: JDBC 'Unterminated quoted string'
Date: Fri, 10 Nov 2000 09:54:43 -0500
Message-ID: <11184.973868083@sss.pgh.pa.us> (raw)
In-Reply-To: <3A0BCC1D.2A2F9F87@ucs.co.za>
References: <1B3D5E532D18D311861A00600865478CF1B50E@exchange1.nt.maidstone.gov.uk>
<3A0BCC1D.2A2F9F87@ucs.co.za>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: tgl@sss.pgh.pa.us, gaf@ucs.co.za, petermount@maidstone.gov.uk
Subject: Re: JDBC 'Unterminated quoted string'
In-Reply-To: <11184.973868083@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox