From: | Christopher Browne <cbbrowne(at)acm(dot)org> |
---|---|
To: | pgsql-advocacy(at)postgresql(dot)org |
Subject: | Re: MySQL 5 comparison |
Date: | 2005-01-06 02:20:03 |
Message-ID: | m3k6qrguy4.fsf@knuth.knuth.cbbrowne.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy |
Clinging to sanity, jdavis-pgsql(at)empires(dot)org (Jeff Davis) mumbled into her beard:
> What caught my eye is the "strict mode". I wonder if they are going
> to start promoting the reporting of errors? Right now MySQL seems to
> have the philosophy that "if the input is wrong, it is better to do
> something than nothing" (e.g. inserting Feb 31st into a date field).
>
> Perhaps they're trying to change that philosophy slowly with this
> strict mode?
You're assuming that there will be some incentive to use this new
mode.
Existing applications that are rife with dependancies on existing
functionality will _break_ if they turn on "strict mode."
And what value is there in fixing them? That doesn't add new
functionality...
No, I don't see a great deal of value in this, outside of _new_
commercial users that are paying for licenses...
--
(reverse (concatenate 'string "moc.liamg" "@" "enworbbc"))
http://www.ntlug.org/~cbbrowne/spreadsheets.html
"A hack is a terrible thing to waste, please give to the
implementation of your choice..." -- GJC
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Browne | 2005-01-06 02:53:52 | Re: MySQL 5 comparison |
Previous Message | David Fetter | 2005-01-06 02:01:39 | Re: MySQL 5 comparison |