| From: | Ragnar Hafstað <gnari(at)simnet(dot)is> |
|---|---|
| To: | tjo(at)acm(dot)org |
| Cc: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: 9.17.5. Row-wise Comparison |
| Date: | 2005-04-07 15:51:54 |
| Message-ID: | 1112889114.5742.17.camel@localhost.localdomain |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
On Thu, 2005-04-07 at 06:44 -0700, TJ O'Donnell wrote:
> it might break in future.
>
> > if (b > 1) then true
> > else if (b = 1 and c > 2) then true
> > else if (b = 1 and c = 2 and d > 3) then true
> > else false
> Your spec sql snippet is like an OR, isn't it, instead
> of an AND as I'm reyling on?
not really.
> After PG is to spec, will the behaviour I now see change?
yes
> > "TJ O'Donnell" <tjo(at)acm(dot)org> writes:
> >
> >>I've been using syntax like
> >>select a from tbl where (b,c,d) > (1,2,3)
> >> to mean
> >>select a from t where b>1 and b>2 and d>3
if b=2, c=1 and d=1 then the expression
(b,c,d) > (1,2,3)
currently evaluates to false, but according to spec,
should evaluate to true.
gnari
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Boes | 2005-04-07 19:48:49 | Re: DROP TYPE without error? |
| Previous Message | TJ O'Donnell | 2005-04-07 13:44:22 | Re: 9.17.5. Row-wise Comparison |