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:
c
> 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);
>>
On Sat, 23 Sep 2006 08:08:58 -0500, Mark Lubratt
<[EMAIL PROTECTED]> wrote:
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).
NO, in my case mySQL had not complained about invalid date
Whoops. My bad. This is a data integrity problem. Not necessarily
ACID compliance. Still bad though...
On Sep 23, 2006, at 8:08 AM, Mark Lubratt wrote:
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
follo
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;
+--+-
Hello,
I spend four hours this morning even before breakfast(!!!) to get
behind this issue.
A customer reported to me: A lot of date entries in our start
changing "magically" to today, without doing anything except viewing
the record!
Result: Using mySQL 4.x or even 5.0.x it's possible
