pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
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:52:30 -0600
Message-ID: <007c01bed7e7$f61f0d80$9e05fea9@dwilson> (raw)
References: <l03130304b3c20462e0db@[147.233.159.109]>

> Yes. Use '\\_%' instead. You see, a backslash is interpreted immediately
as
> "take the next char literally". This passes the underscore literally to
> LIKE. Which is the same as '_%'. If you put a double backslash, the first
> backslash takes the second one literally, thus passing '\_%' to LIKE. And
> then LIKE knows that it should treat the underscore as non-special.

I tried this and it didn't work either.  I eventually got carried away and
did '\\\_%' and it worked.  What a pain!

> 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.


I totally agree here.  There should be some way to turn it off so that those
who are starting out can write standard stuff.

-Dan




view thread (4+ messages)

Message-ID: <007c01bed7e7$f61f0d80$9e05fea9@dwilson>
Permalink:  ../007c01bed7e7$f61f0d80$9e05fea9@dwilson/
Also on:    postgresql.org/message-id/007c01bed7e7$f61f0d80$9e05fea9@dwilson

 · 

reply

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: <007c01bed7e7$f61f0d80$9e05fea9@dwilson>
  References: <l03130304b3c20462e0db@[147.233.159.109]> <007c01bed7e7$f61f0d80$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