I understand the behavior is server-side issue, not JDBC, and we are to be forced to explicitely remove '\0' with the latest server
It's not necessarily the best for me but better than now.
Finally, do you know the thread containing the discussion that triggered the change of server behavior?
> -----Original Message-----
> From: Kris Jurka [mailto:books(at)ejurka(dot)com]
> Sent: Monday, May 22, 2006 4:29 PM
> To: EBIHARA, Yuichiro
> Cc: pgsql-jdbc(at)postgresql(dot)org
> Subject: Re: [JDBC] how to handle data containing '\0'
> On Wed, 17 May 2006, EBIHARA, Yuichiro wrote:
> > I need to handle String data containing '\0' in my Java + JDBC
> > program.
> > Now I have to support two versions of drivers, 7.4 and 8.1, but the
> > behavior of driver depends on versions when I insert this
> String value.
> This was changed between 7.4 and 8.0 when prepared statements
> changed from
> dynamically creating a sql string from the parameters to passing the
> parameters separately. When creating a sql string the
> parameters had to
> be carefully checked for ' and \ so checking for \0 was also
> done. When
> passing the parameters separately there is no need for the '
> and \ checks
> so the \0 check was removed as well either unintentionally or for
> perfomance reasons.
> New server releases for all versions will be out this week
> that fix the
> problem on the server side by explicitly rejecting \0 rather than
> Kris Jurka
In response to
pgsql-jdbc by date
|Next:||From: Kris Jurka||Date: 2006-05-22 08:30:49|
|Subject: Re: how to handle data containing '\0'|
|Previous:||From: Markus Schaber||Date: 2006-05-22 08:12:43|
|Subject: Re: [Pgjdbc-commit] By jurka: Add some more synchronization|