Paul Lambert wrote:
Phillip Smith wrote:
"Having said that, if I switch it to a forward slash it works without
error... odd, given that weenblows standard is backslash."
Yes, but PostgreSQL uses a back-slash as an escape character, which
needs to
be used to escape itself at an application level before the O/S gets
to deal
with it :)
OK, that makes sense, cheers for the help.
Almost correct - PG is moving over to a more SQL standards-based
interpretation of what should be done with backslashes in strings. The
old behaviour will still be available by prefixing a string with E -
E'like this'.
See manuals for details.
--
Richard Huxton
Archonet Ltd
---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster
