Thanks for the clarification.
Michael
On May 17, 2010, at 2:28 PM, Michael Dykman wrote:
> MyISAM does not support transactions so it is inherently in
> 'autocommit mode' all the time. You will run into this with any
> transactional database, be it InnoDB, Falcon, or Oracle and DB2
> installat
MyISAM does not support transactions so it is inherently in
'autocommit mode' all the time. You will run into this with any
transactional database, be it InnoDB, Falcon, or Oracle and DB2
installations for that matter.
For many classes of application, avoiding autocommit and explicitly
creating a
Hello.
In my opinion, you should use SERIALIZABLE transaction isolation level or
SELECT ... LOCK IN SHARE MODE.
"?ngelo M. Rigo" <[EMAIL PROTECTED]> wrote:
> [-- text/plain, encoding 8bit, charset: iso-8859-1, 25 lines --]
>
> Hi
>
> I am using innodb tables to implement transactio
Hi,
> I did some tests earlier where I inserted 100,000 rows into a
> table (table definition below). First, I did it without using
> transactions and it took 243 seconds approximately. Then, I
> did the same test using transactions, and it took 28 seconds.
>
> I am using MySQL v4. Here is the
http://www.innodb.com/ibman.html#InnoDB_transaction_model
Scroll down a bit to Section 8.5
Edward Dudlik
Becoming Digital
www.becomingdigital.com
- Original Message -
From: "Miguel Perez" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, 09 June, 2003 18:44
Subject: INNODB Trans
At 13:22 +0100 3/27/03, Stefan Hinz wrote:
Christian,
It looks like 'drop table' implicitely does a 'commit', at least when
issued by the mysql commandline utility with mysql 3.23.51. This
happens even if it was a temporary heap table as typically used to
emulate subselects.
I think this sho
Christian,
> It looks like 'drop table' implicitely does a 'commit', at least when
> issued by the mysql commandline utility with mysql 3.23.51. This
> happens even if it was a temporary heap table as typically used to
> emulate subselects.
> I think this should be documented. (Or better yet, n
Christian,
- Original Message -
From: "Christian Jaeger" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.mysql
Sent: Thursday, March 27, 2003 1:42 PM
Subject: Innodb transactions and drop table
> Hello
>
> It looks like 'drop table' implicitely does a 'commit', at least when
> issued by
Jeremy,
- Original Message -
From: "Jeremy Zawodny" <[EMAIL PROTECTED]>
To: "Heikki Tuuri" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Monday, April 22, 2002 9:37 AM
Subject: Re: InnoDB transactions with Connection Pooling
> On Mon, Apr 2
On Mon, Apr 22, 2002 at 09:02:54AM +0300, Heikki Tuuri wrote:
> Mark,
>
> if you do not explicitly do
>
> SET AUTOCOMMIT=0
>
> then MySQL automatically calls COMMIT after every SQL statement.
Make that:
SET AUTOCOMMIT=1
Heikki is probably low on coffee. :-)
Jeremy
--
Jeremy D. Zawodny, <
Mark,
if you do not explicitly do
SET AUTOCOMMIT=0
then MySQL automatically calls COMMIT after every SQL statement.
If you set AUTOCOMMIT=0, then you should yourself call COMMIT after each
SELECT so that you do not leave a dangling transaction open in the database
and that you get a fresh snap
11 matches
Mail list logo
