Howdy all,
I've got a series of tables that are used to store a
user's session information. The main table is a very
simple table that stores a GUID and a last access
data-time value. All other tables use the guid as a FK
back to this main table.
The main table's schema is as follows:
CREATE TABLE s_session (
session_guid varchar(36) NOT NULL default '',
last_access_dt datetime NOT NULL default '0000-00-00
00:00:00',
PRIMARY KEY (session_guid)
) TYPE=InnoDB;
What we're seeing is that we get trx deadlocks when
trying to delete rows and occasionally when simply
updating a row (for example, when updating the
last_access_dt when the user moves to a new page in
the app).
Is there any reason that using a GUID as the PK would
cause problems? It seems not, but I really can't
figure out why I would be getting deadlocks. I'm
causing these in a development environment where I'm
the only user!
BTW, I'm using mySQL 4.0.20 on Mac OS X.
Cheers,
Tripp
__________________________________
Do you Yahoo!?
Take Yahoo! Mail with you! Get it on your mobile phone.
http://mobile.yahoo.com/maildemo
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
