| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "David Christensen" <david(at)endpoint(dot)com>, "Robert Haas" <robertmhaas(at)gmail(dot)com>, <pgsql-hackers(at)postgresql(dot)org>, "Wolfgang Wilhelm" <wolfgang20121964(at)yahoo(dot)de> |
| Subject: | Re: SQL compatibility reminder: MySQL vs PostgreSQL |
| Date: | 2010-03-08 20:58:59 |
| Message-ID: | 4B9510B3020000250002FA41@gw.wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy pgsql-hackers |
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I believe we do have consensus that we aren't interested in
> adopting MySQL's nonstandard GROUP BY semantics. I don't recall
> what else there might be a definite "no" for.
TODO "not wanted" entry rewritten to address just this one issue.
The other issues raise in the original post are valid possible
enhancements, or is there something else to list?:
http://archives.postgresql.org/pgsql-hackers/2010-03/msg00257.php
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2010-03-08 21:11:09 | Re: SQL compatibility reminder: MySQL vs PostgreSQL |
| Previous Message | Pierre C | 2010-03-08 20:28:27 | Re: SQL compatibility reminder: MySQL vs PostgreSQL |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2010-03-08 20:59:03 | Re: Explicit psqlrc |
| Previous Message | Alex Hunsaker | 2010-03-08 20:54:33 | Re: Safe security |