Re: Table locking Issue MySQL on Tiger...
Re: Table locking Issue MySQL on Tiger...
- Subject: Re: Table locking Issue MySQL on Tiger...
- From: Kieran Kelleher <email@hidden>
- Date: Thu, 5 May 2005 12:56:38 -0400
Nathan,
Not sure about NaviCat ...... I only use mysql command line client and
a little CocoaMySQL .... different number of rows sounds weird.
if you can, log in via mysql command line and try ALTER TABLE to change
the table type
http://dev.mysql.com/doc/mysql/en/alter-table.html
http://dev.mysql.com/doc/mysql/en/create-table.html
Something like this (not tested) should do it
ALTER TABLE mytable TYPE=innodb;
I use innodb as default for all MySQL tables since they support atomic
transactions and WebObjects will automatically do the
begin/commit/rollback of transactions (saving an EC) for you when you
use innodb which is great to ensure data integrity. With MyISAM, your
editing context save may fail in the middle of saving a bunch of
related EO's and there is no rollback and now your data integrity is
hosed. I think I have only one table that is MyISAM and that's a
read-only lookup table for US zip+4 lat/lng and it has about 70 million
records.
You can set innodb as the default table type by editing /etc/my.cnf to
include the line:
[mysqld]
default-table-type=innodb
-Kieran
________________________________________________________________
Blog: http://webobjects.webhop.org/
On May 5, 2005, at 12:00 PM, Nathan Walker wrote:
I have to use it because I am using stored procedures yes, but I will
try changing the tables to InnoDB, is there much I have to do to get
all newly created tables to use InnoDB instead of MyISAM ? I'm using
Navicat to manage MySQL if you are familiar with that.... Also, I
tried switching one of my tables to InnoDB and everytime I view table
information on it, it reports a different number of total rows ?? is
that normal for InnoDB tables ?? It's very odd... why would it do
that ?
thanks for the info,
Nathan
On May 5, 2005, at 8:06 AM, Kieran Kelleher wrote:
Nathan, you are very brave using MySQL 5.0.4 which is not General
Release yet ;-) If there is no compelling reason to use 5.0.4 (such as
stored procedures), then I think you will definitely solve your
problem by switching to the GA of 4.0 or 4.1. On the other hand you
could try altering your 5.0.4 tables to use InnoDB engine which does
row locks rather than the complete table locks that MyISAM does for a
single row read.
Regards,
-Kieran
________________________________________________________________
Blog: http://webobjects.webhop.org/
On May 5, 2005, at 1:39 AM, Nathan Walker wrote:
I am using MySQL 5.0.4 with WebObjects 5.2.4 on Tiger and since the
upgrade, I have an issue with Table Locking in MySQL. I get this error
if I try to access the table:
Next exception:SQL State:HY000 -- error code: 1099 -- msg: Table
'Invmstr' was locked with a READ lock and can't be updated
I'm not sure if the issue is related to the JDBC driver on Tiger which
I'm using 'mysql-connector-java-3.1.7-bin.jar'......or if it is
related to the MySQL or if it's related to EOF on Tiger ??
I had been developing this application for a couple months now and
have never run into this issue until I did the upgrade. Anybody ever
run into this table locking issue with MySQL ?? The tables engines
are MyISAM..........
Can anybody shed any light about this ?
thx,
nathan
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
email@hidden
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
email@hidden
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden