Re: Backslash as ordinary char vs. not; set via a connection/session

Ken Johanson wrote:
> Tom and folks,
>
> Will it be possible to set this more standard backslash handling
> behavior -- and possibly similar conformance modes... in a way similar
> to how mysql allows? They allow one to issue commands on the connection
> like:
>
> SET SESSION sql_mode = 'NO_BACKSLASH_ESCAPES,IGNORE_SPACE,ANSI'
>
> The advantage to this is that ISPs, etc can, by default, run the
> database with the old/incorrect mode (which is more compatible with the
> correspondingly legacy/broken apps.. and for newer apps to issue that
> command to make the DB act more standards compliant..

postgresql can do that in an even more powerful way - but people tend to
not notice much of it in your case that would be:

ALTER ROLE foo SET standard_conforming_strings='off'

or even:

ALTER DATABASE bar SET standard_conforming_strings='off'

you can do that for nearly all GUCs (like
logging,client_encoding,search_path,....)

Stefan