From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
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 04:47:42 |
Message-ID: | 13655.1112849262@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
"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
> But I see in the manual at:
> http://www.postgresql.org/docs/7.4/interactive/functions-comparisons.html#AEN12735
> that only = and <> operators are supported. Does this section of the manual
> not properly apply to this query? Is the manual in error, or am I
> not understanding?
PG's current code acts as you are supposing, but it is broken because it
doesn't follow the SQL spec, and we will change it as soon as someone
gets around to working on it.
The spec says that this syntax implies a column-by-column ordering,
essentially
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
You can find related discussions in the archives from a few months
back. The spec's semantics correspond exactly to the sort ordering
of a multiple-column btree index, and so there are good reasons why we'd
want to provide that behavior even if it weren't mandated by the spec.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Dinesh Pandey | 2005-04-07 04:51:08 | ar: Command not found. |
Previous Message | TJ O'Donnell | 2005-04-07 03:48:23 | 9.17.5. Row-wise Comparison |