|
|
Invisible wrote:
> Darren New wrote:
>> Invisible wrote:
>>> MySQL isn't transactional = I'm not really interested.
>>
>> It is if you use InnoDB engine tables. Note, it's about five times
>> slower, but it's transactional.
>
> Last I heard, it's transactional yet still not 100% ACID-compliant.
Well, no, but it's transactional. The A and I and D parts, I think. I'm
not sure whether it has support for the C part, since it insists on
having defaults for every data type, so things like declaring a column
"not null" and not providing a value isn't an error.
--
Darren New / San Diego, CA, USA (PST)
It's not feature creep if you put it
at the end and adjust the release date.
Post a reply to this message
|
|