pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <maillist@candle.pha.pa.us>
To: zalman@netcom.com
Cc: zalman@netcom.com
Cc: herouth@oumail.openu.ac.il
Cc: pgsql-sql@postgreSQL.org
Subject: Re: [SQL] How match percent sign in SELECT using LIKE?
Date: Tue, 16 Mar 1999 18:03:58 -0500 (EST)
Message-ID: <199903162303.SAA24348@candle.pha.pa.us> (raw)
In-Reply-To: <199903162255.OAA28174@netcom15.netcom.com>

> Bruce Momjian wrote:
> > That is also an excellent idea.  Just convert their escape to \ inside
> > the parser.  Of course, they still have to use \\ to get a \, as in any
> > string.  Great idea.
> 
> You can even make it fully compliant if you want. (There are of course
> backward compatibility problems. I'm not sure what the Postgres policy is
> on this.)
> 
> - If the escape character is backslash, do nothing.
> - Otherwise, turn all backslashes in the string to double backslashes.

Wow, there are great ideas.  No wonder commercial database have
problems.  We have all this ideas coming from so many people.


> - If the escape character is not set, stop here.
> - Turn all occurences of the escape character into a backslash except
>   where the escape character is doubled, where it should be made into a
>   single occurence.
> (Optionally, if "\n" is just an 'n' character, you can handle double
> occurences of the escape character by turning the first one into a
> backslash.)
> 
> Probably the best bet for PostgreSQL programmers is to always code Like
> clauses with an ESCAPE '\' (or however its written).
> 
> I really wish they'd chosen a character other than underscore for the
> "match one" wildcard... Is there any standard practice for seperating words
> in table names?

Yes, it is a bad choice.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026



view thread (15+ messages)  latest in thread

Message-ID: <199903162303.SAA24348@candle.pha.pa.us>
Permalink:  ../199903162303.SAA24348@candle.pha.pa.us/
Also on:    postgresql.org/message-id/199903162303.SAA24348@candle.pha.pa.us

 · 

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: maillist@candle.pha.pa.us, zalman@netcom.com, herouth@oumail.openu.ac.il
  Subject: Re: [SQL] How match percent sign in SELECT using LIKE?
  In-Reply-To: <199903162303.SAA24348@candle.pha.pa.us>
  References: <199903162255.OAA28174@netcom15.netcom.com> <199903162303.SAA24348@candle.pha.pa.us>

* 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