From: | Lukas Kahwe Smith <smith(at)pooteeweet(dot)org> |
---|---|
To: | David Fetter <david(at)fetter(dot)org> |
Cc: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [OT] MySQL is bad, but THIS bad? |
Date: | 2006-05-18 20:24:38 |
Message-ID: | 446CD806.1050700@pooteeweet.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy pgsql-hackers |
David Fetter wrote:
> On Thu, May 18, 2006 at 09:58:21PM +0200, Lukas Smith wrote:
> In what way is this outdated? Please provide a specific example.
see below ..
>> You have to understand that MySQL evolves just like PostgreSQL does.
>
> If it were true, I would have to understand it, but the way MySQL
> evolves is not even remotely like the way PostgreSQL does. Here are a
> few concrete differences:
Ok, I was not trying to imply that MySQL evolves in the same way .. only
that it also evolves.
> You've made some sweeping allegations here and no specifics.
sweeping allegations?
http://dev.mysql.com/doc/refman/5.0/en/server-sql-mode.html
SET [GLOBAL|SESSION] sql_mode='ALLOW_INVALID_DATES'
That being said the solution is still lacking. I even filed a bug report
over this:
http://bugs.mysql.com/bug.php?id=17998
So I guess you can continue your commentary. Anyways, it was not my
intention to educate PostgreSQL developers about MySQL, only that it
would be wise not to make general comments about MySQL if you do not
follow its development.
regards,
Lukas
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Browne | 2006-05-18 20:25:17 | Re: [OT] MySQL is bad, but THIS bad? |
Previous Message | David Fetter | 2006-05-18 20:18:17 | Re: [OT] MySQL is bad, but THIS bad? |
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Browne | 2006-05-18 20:25:17 | Re: [OT] MySQL is bad, but THIS bad? |
Previous Message | Tom Lane | 2006-05-18 20:23:29 | Re: pgsql: Add simplified sparc8 ASM for solaris_sparc.s, from Alan Stange. |