Re: ALL, ANY bug?

From: Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>
To: tgl(at)sss(dot)pgh(dot)pa(dot)us
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: ALL, ANY bug?
Date: 2001-01-08 07:04:03
Message-ID: 20010108160403W.t-ishii@sra.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

You are right. However, SQL92 spec allows:

select * from t1 where i <> all values(0,1);

which is not allowed in PostgreSQL...
--
Tatsuo Ishii

> Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> writes:
> > It seems ALL and ANY (SOME) have problems with the parser.
>
> I see no problem here. Those are only defined for sub-selects.
> SQL92 8.7 says:
>
> <quantified comparison predicate> ::=
> <row value constructor> <comp op> <quantifier> <table subquery>
>
> <quantifier> ::= <all> | <some>
>
> <all> ::= ALL
>
> <some> ::= SOME | ANY
>
> and that is the only appearance of ANY in the grammar ...
>
> regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Marko Kreen 2001-01-08 07:23:07 Re: patch: contrib/pgcrypto sanity
Previous Message Denis Perchine 2001-01-08 06:40:46 Re: Quite strange crash