Subject: Re: Free RDBMS market case (was Re: "I've got more programmers than you")
From: "Karsten M. Self" <kmself@ix.netcom.com>
Date: Wed, 3 Oct 2001 15:23:37 -0700
Wed, 3 Oct 2001 15:23:37 -0700
on Wed, Oct 03, 2001 at 06:16:07PM -0400, Jim McLaughlin (jim.dogleg@worldnet.att.net)
wrote:

> MySQL doesn't support transactions and therefore wouldn't fly for many
> "bullet proof" requirement specs.
>
> For comparisons sake have a look at:
> http://www.mysql.com/information/benchmarks.html

Does:

    http://www.mysql.com/doc/M/i/Missing Transactions.html

    As MySQL does nowadays support transactions, the following
    discussion is only valid if you are only using the
    non-transaction-safe table types. See section   6.7.1
    BEGIN/COMMIT/ROLLBACK Syntax.  

Which points at:

    http://www.mysql.com/doc/C/O/COMMIT.html

    By default, MySQL runs in autocommit mode. This means that as soon
    as you execute an update, MySQL will store the update on disk.
                                                                                
    If you are using transactions safe tables (like BDB, InnoDB, you can
    put MySQL into non-autocommit mode with the following command:
                                                                                
	SET AUTOCOMMIT=0

    After this you must use COMMIT to store your changes to disk or
    ROLLBACK if you want to ignore the changes you have made since the
    beginning of your transaction.

Peace.

-- 
Karsten M. Self <kmself@ix.netcom.com>        http://kmself.home.netcom.com/
 What part of "Gestalt" don't you understand?              Home of the brave
  http://gestalt-system.sourceforge.net/                    Land of the free
   Free Dmitry! Boycott Adobe! Repeal the DMCA!  http://www.freesklyarov.org
Geek for Hire                      http://kmself.home.netcom.com/resume.html


["application/pgp-signature" not shown]