Received: from candle.pha.pa.us (maillist@s5-03.ppp.op.net [209.152.195.67]) by hub.org (8.9.3/8.9.3) with ESMTP id XAA67202 for ; Wed, 30 Jun 1999 23:43:38 -0400 (EDT) (envelope-from maillist@candle.pha.pa.us) Received: (from maillist@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id XAA06651; Wed, 30 Jun 1999 23:41:05 -0400 (EDT) From: Bruce Momjian Message-Id: <199907010341.XAA06651@candle.pha.pa.us> Subject: Re: [SQL] String concat operator??? In-Reply-To: from Herouth Maoz at "Jun 30, 1999 04:35:28 pm" To: Herouth Maoz Date: Wed, 30 Jun 1999 23:41:05 -0400 (EDT) CC: webmaster@tony.cz, pgsql-sql@postgresql.org X-Mailer: ELM [version 2.4ME+ PL56 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit > At 16:16 +0300 on 30/06/1999, webmaster wrote: > > > > Both id_look and ident are varchars.. So what's wrong with || operator? There > > is an error parsing the querry near || ... > > > > Who is stupid? Me, or postgresql 6.4.2 :) ? It look like legal expression for > > me... > > Old problem... "||" doesn't have associativity, so when you use a||b||c, it > gets mixed up. Solution - use (a||b) || c. Preferably ((a||b)||c). And fixed in 6.5. -- 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