| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, 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 21:11:09 |
| Message-ID: | 4B9567ED.3040005@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy pgsql-hackers |
Tom Lane wrote:
> Yes, I think we should narrowly list things we don't want to do.
> The current wording reads like "we aren't interested in adopting any
> MySQL ideas", which I don't think is actually the project consensus,
> not to mention that it doesn't look good from a PR standpoint.
>
>
>
Indeed. We are always open to good ideas, I hope.
The really obvious candidate of missing functionality from MySQL hasn't
even been mentioned in this thread, AFAIK: some form of insert_or_update.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-03-08 21:17:17 | Re: SQL compatibility reminder: MySQL vs PostgreSQL |
| Previous Message | Kevin Grittner | 2010-03-08 20:58:59 | Re: SQL compatibility reminder: MySQL vs PostgreSQL |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jaime Casanova | 2010-03-08 21:12:51 | disabling log_min_duration_statement from pg_dump? |
| Previous Message | Simon Riggs | 2010-03-08 20:59:03 | Re: Explicit psqlrc |