From: | "Dan Wilson" <dan_wilson(at)geocities(dot)com> |
---|---|
To: | "pgsql general" <pgsql-general(at)postgreSQL(dot)org>, <pgsql-sql(at)postgreSQL(dot)org> |
Subject: | Re: [GENERAL] escaping wildcard chars |
Date: | 1999-07-26 13:48:10 |
Message-ID: | 007b01bed7e7$f48c3880$9e05fea9@dwilson |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-sql |
> 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
From | Date | Subject | |
---|---|---|---|
Next Message | Dan Wilson | 1999-07-26 13:52:30 | Re: [GENERAL] escaping wildcard chars |
Previous Message | Herouth Maoz | 1999-07-26 12:39:36 | Re: [GENERAL] escaping wildcard chars |
From | Date | Subject | |
---|---|---|---|
Next Message | Dan Wilson | 1999-07-26 13:52:30 | Re: [GENERAL] escaping wildcard chars |
Previous Message | Bruce Momjian | 1999-07-26 13:37:49 | Re: [SQL] database design SQL prob. |