| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Max Buvry <Max(dot)Buvry(at)enseeiht(dot)fr>, PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: [HACKERS] Re: Book - SQL Aggregates |
| Date: | 1999-12-07 04:29:54 |
| Message-ID: | 21918.944540994@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> The best way to do that is to display a mess to the user when they try
> COUNT(DISTINCT...). That makes it easy because they see it as soon as
> they try it.
I was actually thinking about trying to implement aggregate(DISTINCT ...),
or failing that, at least understand why it's hard ;-)
At the very least I think I can manage an explicit "DISTINCT not supported"
error message from the parser. Will take this as a TODO item.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan Wieck | 1999-12-07 04:33:14 | Re: [HACKERS] FOREIGN KEY and shift/reduce |
| Previous Message | Lincoln Yeoh | 1999-12-07 04:27:03 | Re: [GENERAL] Oft Ask: How to contribute to PostgreSQL? |