BUG #5483: PQescapeStringConn behaviour ??

From: "Pascal Van Puymbroeck" <ppk(at)zenonpro(dot)be>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #5483: PQescapeStringConn behaviour ??
Date: 2010-05-29 13:20:36
Message-ID: 201005291320.o4TDKaT6050214@wwwmaster.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


The following bug has been logged online:

Bug reference: 5483
Logged by: Pascal Van Puymbroeck
Email address: ppk(at)zenonpro(dot)be
PostgreSQL version: 8.3.5 and 8.3.8
Operating system: Centos 5.4
Description: PQescapeStringConn behaviour ??
Details:

Don't know whether this bug/behaviour is normal or fixed in newer versions.
Didn't have the time to prepare a new installation just to test this.

PQescapeStringConn is intended to facilitate the insertion of say a
streetname with a single quote like " d'alembert ". Using this function on
normal en special strings like " tëxt " (an e with two dots on, quite
common in the dutch and french language) is no problem.

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 !

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Greg Stark 2010-05-29 13:59:52 Re: BUG #5480: Autovacuum interferes with operations (e.g. truncate) on very large databases
Previous Message Bruce Momjian 2010-05-29 02:01:37 Re: BUG #5469: regexp_matches() has poor behaviour and more poor documentation