[GENERAL] automatic rollback?

to be no code in the application that could be doing this. I know this is a long shot but is there any way the changes could be getting rolled back automatically? I'm not using any explicit COMMIT, ROLLBACK, or SAVEPOINT statements. John Gunther ---(end of broadcast

[GENERAL] Confused about locales

stendahl st ènders St. Epson Can someone tell me what combination of PostgreSQL and Linux settings I need for this? It seems like a very basic question, but I'm just dense, I guess. I've tried a half dozen time-consuming configs without success. Thank you. John Gunther

Re: [GENERAL] Locale, encoding, sort order confusion

Alvaro Herrera wrote: For example, with all LC_* parameters set to "en_US.UTF8", I get the following incorrect "order:by": Barn Bcancour Beaupr Did you initdb with locale en_US.UTF8, and also createdb with encoding UTF8? While you can certainly choose mismatching values

Re: [GENERAL] Locale, encoding, sort order confusion

Pretty much any locale (say, en_US for you) with a matching character set should work. Unless you go out of your way, this should be the default setting. I've tried a half dozen time-consuming configs without success. Like what? For example, with all LC_* parameters set to en_US.UTF8, I

[GENERAL] Locale, encoding, sort order confusion

is in sorted order: St-mile stendahl st nders St. Epson Can someone tell me what combination of PostgreSQL and Linux settings I need for this? It seems like a very basic question, but I'm just dense, I guess. I've tried a half dozen time-consuming configs without success. Thank you. John Gunther

[GENERAL] Locale, encoding, sort order confusion

you. John Gunther ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster

[GENERAL] Forcing backslash to be treated as ordinary string character

Doc section 4.1.2.1 says that in future, backslashes will be treated as ordinary string characters. It says to use the E string prefix to ensure that backslashes are permanently treated as escape characters. Question: Aside from dollar quoting (Section 4.1.2.2), is there any way NOW to force

[GENERAL] Forcing backslash to be treated as ordinary string character

Doc section 4.1.2.1 says that in future, backslashes will be treated as ordinary string characters. It says to use the E string prefix to ensure that backslashes are permanently treated as escape characters. Question: Aside from dollar quoting (Section 4.1.2.2), is there any way NOW to force

[GENERAL] locale-specific sort algorithms undocumented?

to ignoring non-alphanumerics. Thanks for sharing any insights. John Gunther Bucks vs Bytes Inc Innovative, advanced web sites for all occasions. ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send