Hi,
[EMAIL PROTECTED] wrote:
Hi list!
I've a problem with transaction
I initiate a transaction with "start transaction". Soon i execute
following query:
* update t1 set t=12; and by I complete I execute rollback but when I do
it I obtain the following thing:
"non-transactional Some changed tab
Hi list,
I am going to change the type of table to InnoDB
Thank!!
Pablo
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Hi,
> I've a problem with transaction
> I initiate a transaction with "start transaction". Soon i execute
> following query:
> * update t1 set t=12; and by I complete I execute rollback but when I do
> it I obtain the following thing:
> "non-transactional Some changed tables couldn't be rolled b
Hi list!
I've a problem with transaction
I initiate a transaction with "start transaction". Soon i execute
following query:
* update t1 set t=12; and by I complete I execute rollback but when I do
it I obtain the following thing:
"non-transactional Some changed tables couldn't be rolled back" an
Hello everyone
I've read about replication mechanism in MySQL, but I've still got some
reservations regarding transactions.
In the manual thay say that in case of a transaction, all update
instructions are hold in a cache, and on commit they are written to the
binary transaction log. After the u
AM
To: 'Paul DuBois'
Cc: [EMAIL PROTECTED]
Subject: RE: MySQL Transaction Problem
I'm sorry, but apparently I'm too green to be able to figure this out.
You are right, when I do the SHOW CREATE TABLE, it tells me my table is
MyISAM. If I use ALTER TABLE Episode TYPE=BDB;, it
I'm sorry, but apparently I'm too green to be able to figure this out.
You are right, when I do the SHOW CREATE TABLE, it tells me my table is
MyISAM. If I use ALTER TABLE Episode TYPE=BDB;, it accepts the command but
does not change the table type.
I am using MySQLD-max-nt, which the manual sa
>I am writing a system that requires transactions. I understand that I need
>to use Transaction-safe tables, such as BDB or InnoDB, but even when I do, I
>get an error when I try to roll back my transaction.
>
>Here is some SQL that illustrates my problem:
>
>I create a table of type BDB (failure
Re: MySQL transaction problem (Again...)
* Carfield Yim <[EMAIL PROTECTED]> wrote on 11.01.01 06:19:
> MySQL 3.23.29 or 3.23.30, with RedHat Linux 7.0, compile from tarball
> source, can't rollback.
>
> Do you mean that it is platform?? There are errors build with RedHat 7.0
* Carfield Yim <[EMAIL PROTECTED]> wrote on 11.01.01 06:19:
> MySQL 3.23.29 or 3.23.30, with RedHat Linux 7.0, compile from tarball
> source, can't rollback.
>
> Do you mean that it is platform?? There are errors build with RedHat 7.0?
Hmm. It certainly does seem so as there have been a few repo
MySQL 3.23.29 or 3.23.30, with RedHat Linux 7.0, compile from tarball
source, can't rollback.
Do you mean that it is platform?? There are errors build with RedHat 7.0?
On Wed, 10 Jan 2001, goEbusiness.com Mail Lists wrote:
> MySQL 3.23.29a-gamma
> Solaris 7
>
> No problems here.
>
> On Wed, 27
11 matches
Mail list logo