From: Dan Wilson <dan_wilson@geocities.com>
To: pgsql general <pgsql-general@postgreSQL.org>
To: pgsql-sql@postgreSQL.org
Subject: Re: [GENERAL] escaping wildcard chars
Date: Mon, 26 Jul 1999 07:48:10 -0600
Message-ID: <007b01bed7e7$f48c3880$9e05fea9@dwilson> (raw)
References: <l03130304b3c20462e0db@[147.233.159.109]>
> I really hate those backslashes. They are blatantly incompatible with
SQL92
> and will cause standard SQL to fail on Postgres, (and of course, Postgres
> code to fail on other databases). There should be a setting, either in the
> backend or in a SET command, such as "BACKSLASH_BEHAVIOR", which will be
> either "literal" or "escape". It can default to the current behavior
> (namely "escape") so that current code won't fail, but will enable people
> to write sane standard code.
Thanks for the info and I totally agree. There should be some type of way
to turn it off or on.
-Dan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: dan_wilson@geocities.com, pgsql-general@postgreSQL.org
Subject: Re: [GENERAL] escaping wildcard chars
In-Reply-To: <007b01bed7e7$f48c3880$9e05fea9@dwilson>
References: <l03130304b3c20462e0db@[147.233.159.109]> <007b01bed7e7$f48c3880$9e05fea9@dwilson>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox