At 4:39 PM +0200 6/17/01, Ismael Touama wrote:
>little bit confuse...
>In your book it's written, MySQL doesn't support (from p.188 to p.193):
> -transaction and commit/rollback
> -FOREIGN KEY ...
> -PROC stocked on the server side and TRIGGER
>And I read it, on the manual...
>Even if solution are given (LOCK, UNLOCK TABLE), I don't understand that
>MySQL is able to put the database in its initial state when an error occurs
>during an update (a manipulation) of its data.
>I'm with binary version 3.23.38.
>I'm sorry but I guess I don't really understand what's under.
Transaction support was added after publication of the book.
>De : Paul DuBois [mailto:paul@stripped]
>Envoye : samedi 16 juin 2001 22:07
>A : Harkins; win32@stripped
>Objet : Re: transactions managment
>At 3:59 PM -0400 6/16/01, Harkins wrote:
>>Oh, I see, you're referring to MaxSQL.
>>I could argue that the need for special tables, etc. negates true
>>inclusion/support of the feature,
>Well, it's really no different than the need to use MyISAM tables to get
>around the limitations of ISAM tables such as the inability to include
>NULL values in indexed columns.
>>but then I know everyone has an opinion,
>>and mine stinks. :)
>No comment. :-)
>>> At 2:49 PM -0400 6/16/01, Harkins wrote:
>>> >===========A version of MySQL does support transactions? Can you
>>> >wasn't aware that any version supported transactions.
>>> Since something like 3.23.15 or so. Grab a current Windows distribution
>>> and run one of the servers with -max in its name.
>>> >> Perhaps your version of MySQL is older and doesn't support
>>> > > or isn't configured to include transaction support? Can you
>> > Paul DuBois, paul@stripped
>Paul DuBois, paul@stripped
Paul DuBois, paul@stripped