From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Herouth Maoz <herouth(at)oumail(dot)openu(dot)ac(dot)il> |
Cc: | webmaster(at)tony(dot)cz, pgsql-sql(at)postgresql(dot)org |
Subject: | Re: [SQL] String concat operator??? |
Date: | 1999-07-01 03:41:05 |
Message-ID: | 199907010341.XAA06651@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
> 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(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Kyle Bateman | 1999-07-01 14:24:47 | Re: [SQL] begin/end/abort work for sequences? |
Previous Message | Bruce Momjian | 1999-07-01 03:26:12 | Re: [SQL] begin/end/abort work for sequences? |