[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mysql
Subject:    Re: Force a COMMIT on InnoDB tables? (set autocommit=0)
From:       patrick <gibblertron () gmail ! com>
Date:       2006-03-31 0:40:52
Message-ID: b043a4850603301640r58322d94jd2fb349d34e1f1a7 () mail ! gmail ! com
[Download RAW message or body]

I've confirmed that this does affect ALL incoming connections.

On 3/30/06, patrick <gibblertron@gmail.com> wrote:
> Is there any way to make this the default behaviour? I did a Google
> search, and it was suggested I put the following line in /etc/my.cnf:
>
> [mysqld]
> init_connect='set autocommit=0'
>
> This works fine, but I worry that this will affect all incoming
> connections regardless of whether or not they are from the
> command-line client. Is there a way to set this just for the client,
> like some option that would go in the [mysql] section?
>
> Patrick
>
> On 3/28/06, Wolfram Kraus <kraus@hagen-partner.de> wrote:
> > patrick wrote:
> > > I'm wondering if there's any way to force updates on InnoDB tables to
> > > require an explicit COMMIT when running queries from the mysql
> > > command-line client (similar to Oracle's command line client)?
> > >
> >
> > set autocommit = 0
> > See
> > http://dev.mysql.com/doc/refman/5.0/en/innodb-and-autocommit.html
> >
> > HTH,
> > Wolfram
> >
> >
> > --
> > MySQL General Mailing List
> > For list archives: http://lists.mysql.com/mysql
> > To unsubscribe:    http://lists.mysql.com/mysql?unsub=gibblertron@gmail.com
> >
> >
>

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/mysql?unsub=mysql@progressive-comp.com


[prev in list] [next in list] [prev in thread] [next in thread]