Re: [HACKERS] Re: Subselects open issue Nr. NEW

From: Michael Meskes <meskes(at)topsystem(dot)de>
To: vadim(at)sable(dot)krasnoyarsk(dot)su (Vadim B(dot) Mikheev)
Cc: pgsql-hackers(at)postgresql(dot)org (PostgreSQL Hacker)
Subject: Re: [HACKERS] Re: Subselects open issue Nr. NEW
Date: 1998-02-17 14:50:00
Message-ID: 199802171450.PAA18468@gauss.topsystem.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Vadim B. Mikheev writes:
> I understand this. And this is how it works currently:
>
> select * from tab where (A,B) >= ANY (select X, Y from tab2);
>
> means: select tuples where A >= X _and_ B >= Y for some tuple from tab2.
> ^^^^^
> 'AND' is used for all Op-s except for '<>' when 'OR' is used.
>
> Question is "should we drop this feature (?) or leave it as is ?"

If we have it, please keep it. Yes, it's not really standard but with some
docu that doesn't hurt. It's still better than an error message IMO. Also
this does make sense as a shortcut version of asking both to be greater or
equal. Did you ever try to do something like that in Oracle? I would have
loved this feature.

Michael

--
Dr. Michael Meskes, Project-Manager | topsystem Systemhaus GmbH
meskes(at)topsystem(dot)de | Europark A2, Adenauerstr. 20
meskes(at)debian(dot)org | 52146 Wuerselen
Go SF49ers! Go Rhein Fire! | Tel: (+49) 2405/4670-44
Use Debian GNU/Linux! | Fax: (+49) 2405/4670-10

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas G. Lockhart 1998-02-17 15:14:45 Re: [HACKERS] results of regression tests: NetBSD/i386 v1.3
Previous Message Meskes, Michael 1998-02-17 14:21:48 RE: [HACKERS] Re: [PORTS] v6.3 release ToDo list and supported p