| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | David Fetter <david(at)fetter(dot)org> |
| Cc: | Rhys Stewart <rhys(dot)stewart(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: regexp searching in arrays not working? |
| Date: | 2007-06-23 02:44:39 |
| Message-ID: | 3789.1182566679@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
David Fetter <david(at)fetter(dot)org> writes:
> On Tue, Jun 19, 2007 at 07:36:02PM -0400, Tom Lane wrote:
>> Since there's no "(array) ANY op scalar" syntax,
> Why isn't there? Is it forbidden by the SQL standard?
Well, the spec has
<quantified comparison predicate> ::=
<row value expression> <comp op> <quantifier>
<table subquery>
<quantifier> ::= <all> | <some>
<all> ::= ALL
<some> ::= SOME | ANY
and not the reverse. The array syntax is an abuse of this notation
and doesn't have the reverse either. I'm not really sure how much
new code would be needed to support the other case, or whether it
would be worth the trouble.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | daniel65456 | 2007-06-23 05:06:35 | Duplicate records returned |
| Previous Message | David Fetter | 2007-06-23 02:13:28 | Re: regexp searching in arrays not working? |