| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | When are subqueries needed |
| Date: | 1999-12-31 06:08:01 |
| Message-ID: | 199912310608.BAA07579@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Can someone summarize when subqueries are required. I thought
aggregates often needed them, but I see now that table aliases can do it
in most cases. I think NOT IN can not be done without subqueries.
Is there a general rule on this? A rule about correlated subqueries?
--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zeugswetter Andreas SB | 1999-12-31 08:39:40 | AW: AW: [HACKERS] correlated subquery |
| Previous Message | Tom Lane | 1999-12-31 05:54:06 | LIKE fixed(?) for non-ASCII collation orders |