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 backslashes in string constants to be treated as
ORDINARY characters?
Thanks
John Gunther <owner@bucksvsbytes.com> writes:
Question: Aside from "dollar quoting" (Section 4.1.2.2), is there any
way NOW to force backslashes in string constants to be treated as
ORDINARY characters?
Not in current releases. CVS tip (8.2-to-be) does have that ability.
Bear in mind though that enabling this is likely to break every client
app in sight, which is why we are moving very slowly on the point.
regards, tom lane