Received: from mx99.openu.ac.il (arbel.openu.ac.il [147.233.32.4]) by hub.org (8.9.3/8.9.3) with ESMTP id KAA21666 for ; Wed, 30 Jun 1999 10:04:54 -0400 (EDT) (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 886174B502; Wed, 30 Jun 1999 16:33:46 +0300 (IDT) 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 AAA455; Wed, 30 Jun 1999 16:36:41 +0300 X-Sender: herouth@shaked.cc.openu.ac.il Message-Id: In-Reply-To: <99063015213102.00441@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 30 Jun 1999 16:35:28 +0300 To: webmaster@tony.cz, pgsql-sql@postgreSQL.org From: Herouth Maoz Subject: Re: [SQL] String concat operator??? 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). Herouth -- Herouth Maoz, Internet developer. Open University of Israel - Telem project http://telem.openu.ac.il/~herutma