Discussion on:
View:
Show:
This is the most helpful article I've seen about MySQL so far! Particularly since it tells how to get features that I generally need in a DB engine. Especially referential integrity.
Thanks for the kudos, guys. My editors heard you. I got a big, fat raise and they've asked for more content from me. Woo hoo!
My next article is a C# reference application to create a web service, Windows app, and Web app to work with a MySQL (or whatever else) back-end.
My next article is a C# reference application to create a web service, Windows app, and Web app to work with a MySQL (or whatever else) back-end.
Good article, Bucky. I learned a lot from it and can put it to good use right away! Thanks.
This is extremely helpful! I knew about the different database engines and where and when to use them...but I'd never read that you can apply different engines to different tables in the same database. This will make the performance of my websitesmuch better and is going to change the paradigm I use for new projects.
Not only explains the engines available and how to use them but also the strengths and weaknesses of each engine.
I can definitely use the info provided.
Thanks!
I can definitely use the info provided.
Thanks!
You're welcome! You're welcome! You're welcome!
I'll see about writing more tutorials on how we can capitalize on the diversity of db engines that can be made use of in MySQL.
I'll see about writing more tutorials on how we can capitalize on the diversity of db engines that can be made use of in MySQL.
Hi,
This article gives a clear summarized view of the MYSQL database engines, Thank you.
This article gives a clear summarized view of the MYSQL database engines, Thank you.
This is a good article which helps one who are facing with common MYSQL error of "Can't create table (errno: 150)", when trying to add a foreign key constraint to existing table.
Root cause for the issue is: parent table & child table will be two different storage engines.
Resolution: Move both the tables to same storage engine
good one..but with one correction
Below statement doesn't work
ALTER TABLE tblMyISAM CHANGE TYPE=InnoDB
Correction: Remove the word 'CHANGE'
Updated statement
ALTER TABLE tblMyISAM ENGINE=InnoDB
Thanks
Harish
Root cause for the issue is: parent table & child table will be two different storage engines.
Resolution: Move both the tables to same storage engine
good one..but with one correction
Below statement doesn't work
ALTER TABLE tblMyISAM CHANGE TYPE=InnoDB
Correction: Remove the word 'CHANGE'
Updated statement
ALTER TABLE tblMyISAM ENGINE=InnoDB
Thanks
Harish
While your article led me to the solution, my version of MySQL required a different syntax:
alter table tableName type=InnoDB;
show table status from databaseName;
alter table tableName type=InnoDB;
show table status from databaseName;
- Keyboard Shortcuts:
- Prev
- Next
- Toggle









































