Posted on Jul29th2020 by Matthias Noback I find it surprising that some years ago we decided that we shouldn't write application logic in our database (e.g. stored procedures) because: Well, anyway, it's clear that we don't want them.

Given that the database supports a uniqueness check by means of adding an index we jump in and add it to every column we feel should be unique.

You'd be able to sign up with that person's email address, while providing your own password, and log in with it.

The biggest advantage of decoupling from the database and its schema is that you are in the position to model everything that's important for your application's data integrity in code.
Newsletter

Get the latest Laravel/PHP jobs, events and curated articles straight to your inbox, once a week

Glimpse streamlines Laravel development by seamlessly deploying GitHub pull requests to preview environments with the help of Laravel Forge. Glimpse streamlines Laravel development by seamlessly deploying GitHub pull requests to preview environments with the help of Laravel Forge.
Fathom Analytics | Fast, simple and privacy-focused website analytics. Fathom Analytics | Fast, simple and privacy-focused website analytics.
Shirts painstakingly handcrafted by under-caffeinated developers. Shirts painstakingly handcrafted by under-caffeinated developers.
Community Partners