On Sep 23, 2006, at 9:22 AM, Ruslan Zasukhin wrote:
From: Mark Lubratt <[EMAIL PROTECTED]>
Date: Sat, 23 Sep 2006 08:08:58 -0500
One of the many gotchas when using MySQL. And the reasons I refuse
to use it. By default MySQL is not ACID compliant. Try the
following:
from 5.1.11-beta:
create table test (x tinyint, d date);
insert into test values (300, '2006-02-30');
select * from test;
+----------+----------------+
| x | d |
+----------+----------------+
| 127 | 0000-00-00 |
+----------+----------------+
MySQL has changed the values stored from the values you insert
without any complaints whatsoever. This is a major violation if the
I in ACID (integrity).
You sure that there is no ANY signal?
I remember that in mySQL exists WARNING log or something like this..
Where they do or can do silent drop of warning message.
I can't find any such log.
As I said in a previous email. This doesn't have anything to do with
ACID compliance (my mistake); but, rather general data integrity
(what you put in is what you get out). If you create the above table
with the InnoDB table handler (ACID compliant), you still get the
same result.
Mark
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
