Can Entity support MyISAM tables just as easily?

Discussion of open issues, suggestions and bugs regarding ADO.NET provider for MySQL
Post Reply
Posts: 6
Joined: Mon 27 Oct 2008 13:57

Can Entity support MyISAM tables just as easily?

Post by notken » Thu 29 Jul 2010 06:52

Hi there. I'm just starting a new project, and using Entity Framework 4 for the first time, with Devart's MySql Connect product.

I've created my model and I've noticed it uses INNODB, which makes sense. However, I'm more comfortable with MyISAM, and can happily live without transactions and foreign keys. I've edited the db create file to use MyISAM and deleted the foreign key definitions, and so I'll be experimenting myself using just that anyway, but I wondered if there was anything I'm going to run in to. I'm happy to control referential integrity on deletes in my code, so this is purely from a Devart/Entity point of view.

I may well opt to return to INNODB anyway, but I need to consider any potential pitfalls of using either engine at this early stage in the project's development.

Thanks for your time.

Devart Team
Posts: 2919
Joined: Mon 07 Jul 2008 13:16

Post by AndreyR » Fri 30 Jul 2010 12:23

I have made a couple tests, everything works smoothly.
As far as you are aware about the limitations of MyISAM engine, there should be no problems.

Post Reply