Received: from mx99.openu.ac.il (arbel.openu.ac.il [147.233.32.4]) by hub.org (8.9.2/8.9.1) with ESMTP id EAA49147 for ; Wed, 17 Mar 1999 04:57:45 -0500 (EST) (envelope-from herouth@oumail.openu.ac.il) Received: from talmon.openu.ac.il (talmon.openu.ac.il [147.233.32.11]) by mx99.openu.ac.il (Postfix) with ESMTP for id 1C8824B49E; Wed, 17 Mar 1999 11:57:42 +0200 (IST) Received: from [147.233.159.109] (mac-herouth.pc.openu.ac.il) by talmon.openu.ac.il (Netscape Messaging Server 3.54) with ESMTP id AAA2D50; Wed, 17 Mar 1999 11:59:22 +0200 X-Sender: herouth@shaked.cc.openu.ac.il Message-Id: In-Reply-To: <199903162226.RAA20904@candle.pha.pa.us> References: <199903162051.MAA01651@netcom15.netcom.com> from Zalman Stern at "Mar 16, 1999 12:51:41 pm" Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 17 Mar 1999 11:58:46 +0200 To: Bruce Momjian , zalman@netcom.com (Zalman Stern) From: Herouth Maoz Subject: Re: [SQL] How match percent sign in SELECT using LIKE? Cc: pgsql-sql@postgreSQL.org At 00:26 +0200 on 17/03/1999, Bruce Momjian wrote: > > > > But I don't have in depth knowledge of the Postgres SQL parser and > > evaluator so I may be way off base. > > 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. Just a quick note about compliance: It has to work two ways. That is, if someone imports an SQL script from his previous database (or don't you think people will be migrating *to* postgres, only *from* it?), it has to work. Thus, if someone has a script written to the SQL92 standard, he is allowed to use a construct like ...WHERE pathname LIKE 'C:\WINDOWS\%' Without encountering oddities. Herouth -- Herouth Maoz, Internet developer. Open University of Israel - Telem project http://telem.openu.ac.il/~herutma