standard_conforming_strings
in [PgSql]
|
From: Robert Haas on 19 Jul 2010 22:00 On Mon, Jul 19, 2010 at 8:32 PM, Robert Haas <robertmhaas(a)gmail.com> wrote: > On Mon, Jul 19, 2010 at 5:04 PM, Peter Eisentraut <peter_e(a)gmx.net> wrote: >> On s�n, 2010-07-18 at 09:42 -0700, David E. Wheeler wrote: >>> On Jul 18, 2010, at 1:35 AM, Peter Eisentraut wrote: >>> >>> > I think there are two ways we can do this, seeing that most appear to be >>> > in favor of doing it in the first place: �Either we just flip the >>> > default, make a note in the release notes, and see what happens. �Or we >>> > spend some time now and make, say, a list of driver versions and >>> > application versions that work with standard_conforming_strings = on, >>> > and then decide based on that, and also make that list a public resource >>> > for packagers etc. >>> >>> Do both. Turn them on, then make a list and inform driver maintainers who need to update. They've got a year, after all. >> >> Here we go then: >> http://wiki.postgresql.org/wiki/Standard_conforming_strings > > Looks like a good start. �We might want to make an "open items for > 9.1" page and, as a first such open item, add a link to this page. > > Since it seems we have consensus, I will commit the patch. So it turns out that (at least) the hstore and ECPG regression tests depend on the default setting of standard_conforming_strings. I have taken a crack at fixing this... -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise Postgres Company -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Marko Kreen on 20 Jul 2010 06:31 On 7/20/10, Peter Eisentraut <peter_e(a)gmx.net> wrote: > On s�n, 2010-07-18 at 09:42 -0700, David E. Wheeler wrote: > > On Jul 18, 2010, at 1:35 AM, Peter Eisentraut wrote: > > > > > I think there are two ways we can do this, seeing that most appear to be > > > in favor of doing it in the first place: Either we just flip the > > > default, make a note in the release notes, and see what happens. Or we > > > spend some time now and make, say, a list of driver versions and > > > application versions that work with standard_conforming_strings = on, > > > and then decide based on that, and also make that list a public resource > > > for packagers etc. > > > > Do both. Turn them on, then make a list and inform driver maintainers who need to update. They've got a year, after all. > > > Here we go then: > http://wiki.postgresql.org/wiki/Standard_conforming_strings There is two sorts of support: 1. Detect stdstr on startup and use that setting. 2. Detect online changes to stdstr and follow them. AFAICS psycopg does not support 2). Should we care about that? There are probably other drivers with partial support. -- marko -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Peter Eisentraut on 20 Jul 2010 15:34 On tis, 2010-07-20 at 13:31 +0300, Marko Kreen wrote: > > http://wiki.postgresql.org/wiki/Standard_conforming_strings > > There is two sorts of support: > > 1. Detect stdstr on startup and use that setting. > > 2. Detect online changes to stdstr and follow them. > > AFAICS psycopg does not support 2). Should we care about that? > > There are probably other drivers with partial support. I think a driver could also just use E'' when it sees a backslash in the string. -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
First
|
Prev
|
Pages: 1 2 3 Prev: [HACKERS] standard_conforming_strings Next: Synchronous replication |