true) // don't bother rolling it back if ctor fails
{
// Set the transaction isolation level and scope as the user wishes
Query q(conn_.query("SET "));
if (scope == session) q << "SESSION ";
if (scope ==
Apologies for a late reply.
1) The query that tries to insert the invalid entry into Table2 fails.
Therefore, if you have 3 separate queries as in the first case, the
last one fails, but the first 2 are successful. In the second case,
they're all in one query, and if one fails, they all fail.
F
Hi.
I have a few questions regarding the transaction levels in mysql 5.0.20
using InnoDB tables.
we are trying to populate two tables in the two following ways, we thought
that they would be equivalent, apparently they are not.
have a look at the following (questions last).
FIRST METHOD:
=
,
not the gap before it. So, parallel INSERTs are possible and they cause
a 'duplicate' error.
> In the transaction isolation level,Database send some "duplicate entry"
> message to me.
> Why?
>
>
In the transaction isolation level,Database send some "duplicate entry"
message to me.
Why?
_
与联机的朋友进行交流,请使用 MSN Messenger: http://messenger.msn.com/cn
--
MySQL General Mailing List
For list archives: http://lists
ying that SET SESSION TRANSACTION
ISOLATION LEVEL READ COMMITTED would be ignored for MyISAM tables. I may
open an official support call to verify.
> If you're using a newer version of our JDBC driver (3.1.x), you can
> always add "useLocalSessionState=true" to avoid having to d
at the query log, I'm now getting...
>
> SHOW VARIABLES
>
> ...once per connection
>
> followed by...
> SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED
>
> -> followed by one or more...
> ^ SELECT
> ^
> ^ followed by...
&
lowed by...
SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED
-> followed by one or more...
^ SELECT
^
^ followed by...
^ SET autocommit=1
^ SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED
^
<- this pattern repeats until the final Quit for the connection.
should happen?
>
> Please correct me if I am wrong, but using the READ_COMMITTED
> transaction isolation level, I should be achieving what I want, right?
> I used the following syntax to ensure that the read_committed level
> (which is apparently default to Mysql) is enforced:
>
g the READ_COMMITTED
transaction isolation level, I should be achieving what I want, right?
I used the following syntax to ensure that the read_committed level
(which is apparently default to Mysql) is enforced:
set global transaction isolation level read_commited;
I tried using MySQL v4 beta, but same
-Jianliang
-Original Message-
From: Heikki Tuuri [mailto:[EMAIL PROTECTED]]
Sent: 2002?10?8? 9:56
To: Jianliang Zhao; Mark Matthews
Cc: [EMAIL PROTECTED]
Subject: Re: transaction isolation level
Jianliang,
I tested that with two mysql clients, and it appeared to work ok. Check with
S
--+
1 row in set (0.00 sec)
mysql>
- Original Message -
From: "Jianliang Zhao" <[EMAIL PROTECTED]>
To: "Heikki Tuuri" <[EMAIL PROTECTED]>; "Mark Matthews"
<[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, October 08,
i Tuuri [mailto:[EMAIL PROTECTED]]
Sent: 2002?10?8? 0:22
To: Mark Matthews
Cc: [EMAIL PROTECTED]
Subject: Re: transaction isolation level
Hi!
- Original Message -
From: "Mark Matthews" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.mysql
Sent: Tuesday, October 08, 2002
Hi!
- Original Message -
From: "Mark Matthews" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.mysql
Sent: Tuesday, October 08, 2002 5:07 AM
Subject: Re: transaction isolation level
> Jianliang Zhao wrote:
...
> >>I am connecting to MySql 3.23(innodb) w
o:[EMAIL PROTECTED]]
>Sent: 2002?10?7? 17:36
>To: Jianliang Zhao
>Cc: [EMAIL PROTECTED]
>Subject: Re: transaction isolation level
>
>
>On Mon, Oct 07, 2002 at 05:30:57PM -0700, Jianliang Zhao wrote:
>
>
>>Hi,
>>
>>I am connecting to MySql 3.23(inn
ao
Cc: [EMAIL PROTECTED]
Subject: Re: transaction isolation level
On Mon, Oct 07, 2002 at 05:30:57PM -0700, Jianliang Zhao wrote:
> Hi,
>
> I am connecting to MySql 3.23(innodb) with
> mysql-connector-java-2.0.14-bin.jar. I set the global transaction
> isolation level to READ C
On Mon, Oct 07, 2002 at 05:30:57PM -0700, Jianliang Zhao wrote:
> Hi,
>
> I am connecting to MySql 3.23(innodb) with
> mysql-connector-java-2.0.14-bin.jar. I set the global transaction
> isolation level to READ COMMITTED. However, I still couldn't see the
> committed chan
Hi,
I am connecting to MySql 3.23(innodb) with mysql-connector-java-2.0.14-bin.jar. I set
the global transaction isolation level to READ COMMITTED. However, I still couldn't
see the committed changes through JDBC client. Does anyone know about this issue?
Thanks,
Jian
Jeremy,
look at http://www.innodb.com/ibman.html and http://www.innodb.com/todo.html
about InnoDB isolation levels.
Currently, SET TRANSACTION ISOLATION LEVEL does not have any effect on
MyISAM, BDB, or InnoDB.
The standard isolation level of InnoDB is REPEATABLE READ (you can also call
that
19 matches
Mail list logo