| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | sumit <sumit(at)gdit(dot)iiit(dot)net> |
| Cc: | pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: Patch for adding DATACUBE operator |
| Date: | 2003-06-30 14:33:54 |
| Message-ID: | 4592.1056983634@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
sumit <sumit(at)gdit(dot)iiit(dot)net> writes:
> In keeping with this, we first define the syntax of a CUBE statement as follows:
> SELECT <field list><aggregate list>
> INTO <destination table>
> FROM <table expression>
> WHERE <search condition>
> GROUP BY <aggregate list>
> HAVING <search condition>
> WITH CUBE;
SQL99 defines a GROUP BY CUBE(...) operation, which seems to do the same
thing as this. Why are you using a nonstandard syntax?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Carlos Guzman Alvarez | 2003-06-30 14:49:26 | Re: Question about array read using protocol 3.0 implementation |
| Previous Message | scott.marlowe | 2003-06-30 12:19:19 | Re: When will table partitioning be available.. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2003-06-30 15:37:17 | Re: polymorphic arguments and return type for PL/pgSQL |
| Previous Message | Serguei Mokhov | 2003-06-30 14:13:19 | Re: pgAdmin3 translation request into Russian |