This content has been marked as final. Show 2 replies
MyISAM tables aren't designed to be transaction-safe. That's what the InnoDB table type is for.
From that tutorial:
"MyISAM tables are very fast for SELECTs, but they have some serious drawbacks when it comes to locking. These shortcomings are what prevented MySQL from implementing some key database features, including transactions."
After making a copy of the tables:
I used MySQLAdmin to convert each of the tables to InnoDB. It displayed the correct "alter table table_name type=innobd;" box before each change.
Before the changes, the three tables showed the same record count. After the changes, they were wildly different. But, (with no changes to the web pages) the application opens OK and I can call up records. Did the conversion get rid of some records or what?
Also, one of the pages (that uses a lot of convoluted logic for the display) takes a lot longer to appear than it used to. All the other pages are open fine and display their forms, etc.. Updates seem a little slower, but not too bad.
Why is the record count different in the three tables? Why might the one page be running slower? (Do I need to make any changes in the original web page code?)
Prior to the conversion, the three MyISAM tables (*.MYD, *.MYI, & *.frm) were all stored in the C:\\Program Files\MySQL\MySQL Server 5.0\data\my_data directory. Now that directory only holds ".frm" files. Where did the conversion put the new tables?
I haven't yet tested the cftransactions to verify they work. That's next.