Hi all.
From the Mysql Documentation:
If you attempt to enable read_only while other clients hold explicit table
locks or have pending transactions, the attempt blocks until the locks are
released and the transactions end. While the attempt to enable read_only is
pending, requests by other
What version do you use? David.
-Original Message-
From: Viacheslav Biriukov [mailto:v.v.biriu...@gmail.com]
Sent: Monday, November 28, 2011 7:09 AM
To: mysql@lists.mysql.com
Subject: Read_only and InnoDB transactions
Hi all.
From the Mysql Documentation:
If you attempt to enable
: Read_only and InnoDB transactions
Hi all.
From the Mysql Documentation:
If you attempt to enable read_only while other clients hold explicit table
locks or have pending transactions, the attempt blocks until the locks
are
released and the transactions end. While the attempt to enable
Biriukov [mailto:v.v.biriu...@gmail.com]
Sent: Monday, November 28, 2011 9:20 AM
To: David Lerer
Cc: mysql@lists.mysql.com
Subject: Re: Read_only and InnoDB transactions
MySQL Community Server 5.1.59 on the Centos 5.7
2011/11/28 David Lerer dle...@us.univision.commailto:dle...@us.univision.com
What
Hello, I'm currently writing a python program that scans some web directories
and then stores some information in a local database. I'm playing with using
InnoDB for this application as a test bed for using InnoDB in further
applications, but I'm running into a couple issues.
When I try to
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
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
Hi,
I am facing a strange problem with INNODB. My application communicates with
mysql server using JDBC. I am using mysql 5.1 version.
Even after issuing connection.commit() / connection.rollback() commands, still
on the sql side the transactions are not getting closed properly. In our
behavior).
R.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 23, 2006 9:31 AM
To: mysql@lists.mysql.com
Subject: Problem with INNODB transactions
Hi,
I am facing a strange problem with INNODB. My application communicates
with mysql server
Subject: RE: Problem with INNODB transactions
What connection pool code are you using? My guess is that the problem is
in your code somewhere. Either transactions are not being closed (i.e.
because of a connection pool flaw maybe?) or you have two threads trying
to update the same row at the same
Hi,
We have moved from Mysql4 to MySQL5 and are currently planning our new database
schema. In this new approach we would like to move to InnoDB's storage engine
for transaction support and still want to use MySQL's FULLTEXT search
capabillities. And to make things easy we also want to
Hi
I am using innodb tables to implement transactions on my system
here is the pseudo code:
SET AUTOCOMMIT = 0
BEGIN
if(erro){
ROLLBACK
} else {
COMMIT
}
When i do commit a transaction and list the data im my web aplication the
records are not acurate .
How can i get the rigth data
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 transactions on my
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 table
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
Hi :
I would like to know what happen if I start a transaction using BEGIN
command I do some insert or update statements, and just before executing a
ROLLBACK or COMMIT command I get disconnected and I can't execute those
commands.
For how long does the table remain locked, or in other words
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
Hello
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, not do a
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
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, not
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
I came accross a problem porting our tv listings system from postgres to
mysql with InnoDB.
With InnoDB tables, read-only transactions started after a read-write
transaction touching the same rows are able to read data as it was before
the read-write transaction began; UNLESS the read-only
...
Subject: Bug? InnoDB transactions and temporary table hanging
From: Samuel Liddicott
Date: Thu, 6 Feb 2003 10:57:13 -
I came accross a problem porting our tv listings system from postgres to
mysql with InnoDB.
With InnoDB tables, read-only transactions started after a read-write
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, [EMAIL
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 22, 2002 at 09:02:54AM +0300, Heikki Tuuri wrote
snapshot of the database in each consistent read.
Best regards,
Heikki Tuuri
Innobase Oy
---
InnoDB - transactions, row level locking, and foreign key support for MySQL
See http://www.innodb.com, download MySQL-Max from http://www.mysql.com
- Original Message -
From: Mark Hazen [EMAIL
George,
the default in MySQL is
set autocommit = 1;
To be able to do rollbacks you have to execute
set autocommit = 0;
Then you can do
insert into ...;
rollback;
I assume you specified in CREATE TABLE ... (...) TYPE=INNODB?
Regards,
Heikki
Copied message:
.
Hello everybody
27 matches
Mail list logo
