I am using MySQL version 4.0.11 gamma on Linux 7.1 and have just
experienced the following problem:
INSERTed a record into a InnoDB table, then used SELECT to retrieve the
recordID (auto numbered field) from the same table using a key. The
SELECT returned the proper ID. However, when
Did you commit the transaction?
Kevin Carlson wrote:
I am using MySQL version 4.0.11 gamma on Linux 7.1 and have just
experienced the following problem:
INSERTed a record into a InnoDB table, then used SELECT to retrieve
the recordID (auto numbered field) from the same table using a key.
gerald_clark wrote:
Did you commit the transaction?
Yes, the transaction was committed. I was using MyCC at the same time
the anomaly occurred, also. Could this have had anything to do with it?
Kevin Carlson wrote:
I am using MySQL version 4.0.11 gamma on Linux 7.1 and have just
Kevin Carlson mailto:[EMAIL PROTECTED]
on Thursday, October 30, 2003 2:38 PM said:
Yes, the transaction was committed. I was using MyCC at the same time
the anomaly occurred, also. Could this have had anything to do with
it?
What was the star date of said anomaly?
TEEHEE!
Chris.
--
Yes, the transaction was committed. I was using MyCC at the same time
the anomaly occurred, also. Could this have had anything to do with
it?
I am new to MySQL - do you *have* to commit the transaction after the
insert?
What is the benefit of the commit - does it do anything?
-Erich-
* Erich Beyrent
[...]
I am new to MySQL - do you *have* to commit the transaction after the
insert?
Only if you are in an active transaction. MySQL supports multiple table
types, both transcational and non-transactional. BDB and InnoDB are the only
transcational table types in MySQL, and by
