Robert Treat wrote: > On Wednesday 24 August 2005 02:01, Jim C. Nasby wrote: > > On Wed, Aug 24, 2005 at 12:26:21AM -0400, Tom Lane wrote: > > > "Jim C. Nasby" <[EMAIL PROTECTED]> writes: > > > > Is the intention that standard_conforming_strings will always be > > > > read-only? > > > > > > For the moment it's read-only false; the long-term goal is that it will > > > be read-only true. In between we will have a release or three where it > > > is modifiable to some extent. I personally think it would be a *bad* > > > idea if it were a mere USERSET variable --- we learned from the > > > autocommit fiasco that changing fundamental semantics on a whim does > > > not work. But there will need to be some way to alter it for testing > > > purposes during the interregnum. > > > > The 'autocommit fiasco' isn't ringing a bell right now, so I'll take > > your word for it. :) > > > > Bruce, can you add some info about this to > > http://candle.pha.pa.us/cgi-bin/pgescape ? I intend to link to that when > > I submit a patch to the release notes that links to more info on the > > individual items. > > it seems odd to me to be linking to random pages on the net from the release > notes... could that content be folder into the docs themselves and then a > pointer to the relevent section of the docs be given instead?
Yes, I am thinking that is best too. I have added this to the release notes: Also, use two single-quotes ('') to embed a literal single-quote in a string, rather than the PostgreSQL-supported syntax of backslash single-quote (\'). The former is standards-conforming and does not require the use of the E'' string syntax. You can also use the $$ string syntax, which does not treat backslashes specially. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster