BUG #5483: PQescapeStringConn behaviour ?? - Mailing list pgsql-bugs

From Pascal Van Puymbroeck
Subject BUG #5483: PQescapeStringConn behaviour ??
Date
Msg-id 201005291320.o4TDKaT6050214@wwwmaster.postgresql.org
Whole thread Raw
Responses Re: BUG #5483: PQescapeStringConn behaviour ??  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
The following bug has been logged online:

Bug reference:      5483
Logged by:          Pascal Van Puymbroeck
Email address:      ppk@zenonpro.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 !

pgsql-bugs by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: BUG #5477: CREATE DOMAIN NOT NULL constraints not always enforced for INSERT with subquery
Next
From: Bruce Momjian
Date:
Subject: Re: BUG #5469: regexp_matches() has poor behaviour and more poor documentation