Re: BUG #5483: PQescapeStringConn behaviour ??

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Pascal Van Puymbroeck" <ppk(at)zenonpro(dot)be>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5483: PQescapeStringConn behaviour ??
Date: 2010-05-29 21:15:57
Message-ID: 24389.1275167757@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"Pascal Van Puymbroeck" <ppk(at)zenonpro(dot)be> writes:
> However if the " " character is at the end of a string like the name of a
> country in dutch "Itali" this PQescapeStringConn function adds two
> spaces. so "Belgi" becomes "Belgi ". The error is set to 1 which
> indicates we can't trust the outcome. But I don't see why he has a problem
> with that character at the end of the string and not in the middle !

This isn't tremendously surprising if you're feeding data to the
function that is not in the encoding it expects (which is what the error
flag almost certainly is telling you). It may be able to detect the
problem in some cases and not others.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Sakari A. Maaranen 2010-05-29 21:44:26 Re: BUG #5480: Autovacuum interferes with operations (e.g. truncate) on very large databases
Previous Message Bruce Momjian 2010-05-29 21:00:55 Re: BUG #5469: regexp_matches() has poor behaviour and more poor documentation