-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160


> The main problem of enabling standard_conforming_strings is
> that applications and/or programming language DB APIs are
> not prepared to support this. I don't see a change in DB
> APIs (that I know of -- Python, Perl, and PHP) to add
> support for producing a string according to
> standard_conforming_strings parameter.

Perl (DBD::Pg anyway) has been compatible since May 2008.

As one of the more vocal critics of the 8.3 implicit casting
incident, I say +1 on making the change. Unlike casting, it's
a simple GUC change to "fix", and now (9.0) is the time to
do it.

- --
Greg Sabino Mullane greg(at)turnstep(dot)com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201002031233
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8


-----BEGIN PGP SIGNATURE-----

iEYEAREDAAYFAktps4oACgkQvJuQZxSWSshAIgCg6wxvgVasOksQ8JQaFOeaSQEu
zZwAn0UqIG7Oti6BJVeJYTEx6b7VsZjf
=HJcB
-----END PGP SIGNATURE-----

In response to

• Re: PG 9.0 and standard_conforming_strings at 2010-01-30 14:55:01 from Euler Taveira de Oliveira

Responses

• Re: PG 9.0 and standard_conforming_strings at 2010-02-03 17:39:21 from Tom Lane
• Re: PG 9.0 and standard_conforming_strings at 2010-02-03 18:20:57 from Robert Haas

pgsql-hackers by date

Next:	From: Tom Lane	Date: 2010-02-03 17:39:21
	Subject: Re: PG 9.0 and standard_conforming_strings
Previous:	From: Tom Lane	Date: 2010-02-03 17:31:12
	Subject: Re: Hot Standby and VACUUM FULL