Kevin Grittner wrote: > direction PostgreSQL is headed is to drop the nonstandard escapes, > unless an extended literal is explicitly used. I've attached a patch > which supports this as a configure option, using a > --enable-standard-strings switch.
There is already a run-time configuration option standard_conforming_strings which does what you seem to have in mind. -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
