It is difficult to write standard-compliant code in Postgres.
There are a lot of constructs which have SQL equivalents but are still used
widely, even in samples in docs!
For example, there are suggestions using
now()::CHAR!=foo
while the correct way is
CAST(CURRENT_DATE AS CHAR)<>foo
now() function, :: and != operators should be removed from language.
I like the Python logic: there is one way
Postgres uses C logic: there are multiple ways.
Bruce seems to attempt start this process trying implement
escape_string_warning in postgresql.conf . However, this is only very minor
step. Please clean Postgres.
Andrus.