At 12:40 PM 7/30/2006, you wrote:
Hello!
Am 30.07.2006 um 18:40 schrieb mos:
The Cayenne framework is using a a single table to keep the primary
keys (PK) for its objects. The method accessing this table is
surrounded by lock / unlock commands, so no other thread can read the
same PK from the
Hello!
Am 30.07.2006 um 18:40 schrieb mos:
The Cayenne framework is using a a single table to keep the primary
keys (PK) for its objects. The method accessing this table is
surrounded by lock / unlock commands, so no other thread can read the
same PK from the table while another thread is curre
At 05:43 AM 7/29/2006, you wrote:
Dear list,
we are running a Mysql 5.0.22 server that is accessed by a number of
java web applications (jdbc driver 3.1) over the network. The
database layer was realized using the Cayenne framework and InnoDB
was chosen as the table type. All applications share
Hi All,
Thank you for u r valuable suggestions. I am trying to implement Sequence.
As i should not use AUTOINCREMENT, and Locking a table will slower my
application.
Thank you once again.
anted mysql to handle the
"unique" id. MySQL would return only the minorid (autoincrement field) on an insert. Just some ideas to keep uniqueness when you
have things running concurrently.
- Original Message -
From: "Burke, Dan" <[EMAIL PROTECTED]>
To: "Dan
/MySQL_Sequences
I'd also welcome any criticisms on it if anyone else is bored enough to
check it out.
Dan.
-Original Message-
From: Dan Buettner [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 27, 2006 8:55 AM
To: balaraju mandala
Cc: mysql@lists.mysql.com
Subject: Re: concurrency problem
Use a transaction and an InnoDB table.
http://dev.mysql.com/doc/refman/5.0/en/transactional-commands.html
Or, use the LOCK TABLES command:
http://dev.mysql.com/doc/refman/5.0/en/lock-tables.html
An ideal solution (in my mind) is to use a stored procedure to read the
table, increment the current
