Entity Framework by with a Mysql Database

 

A pictorial representation of how Entity Framework, in the world of code, would look if it was a corporeal object.
A pictorial representation of how Entity Framework, in the world of code, would look if it was a corporeal object.

The problem with using a database, when you have another primary source of information, is that the database needs to be updated. Constantly. If someone forgets to update the database, then you will be relying on information that is old/erroneous and not updated. That’s a huge risk. It’s the type of thing that you want to do only if your staff are disciplined, and the gravity of failure is low, should they forget. But if the reverse is true, then you’re sure to eat humble pie, and cause a lot of needless trouble and expense for yourself and all you deal with.

There was a political war over the implementation: I was for using the original database, and the boss was for creating a new one. Accuracy vs speed. Speed won the victory. And I must oblige by constantly updating a database with panel information.

Anyways enough with the back ground. [Here’s how you do it.]( https://forums.mysql.com/read.php?174,601264,601264)

And I’ll paste it in below, just in case the link fails, as it is wont to do, inevitably – at some time in the future.

 


Comments

Leave a Reply

Your email address will not be published. Required fields are marked *