This is a continuation of my earlier post on Database Design. This time I will talk about some nuts and bolts in a database, and how many of them can help, and sometimes even break your application
Just a small collection of recommended courses for web developers.
You might think that the way your store your data isn't really that important. Well it's more important than you think it is. A good database design just like good clean code is the key to performance, not only for the end user but also for you the developer. A poor database model just like poorly written code will slow you down and furthermore it will slow your database queries down which results in a slow application. Just like with the SOLID principles there are some things to consider when developing a database model.
Why write this little guide since Laravel uses Eloquent to talk to the database? The answer is simple, the errors the database returns are SQL errors and if you don't know how to interpret them then your life as a developer will be harder.
This site uses Torchlight for syntax highlighting.