Timeline for Handle all authentication logic in database or code?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 13, 2012 at 13:28 | vote | accept | Snuffleupagus | ||
| Jun 13, 2012 at 13:28 | vote | accept | Snuffleupagus | ||
| Jun 13, 2012 at 13:28 | |||||
| Jun 12, 2012 at 21:03 | comment | added | BryanH | A good rule of thumb is assuming data goes into the database without error, will the data be stored as expected, and can it be retrieved properly? It isn't the code's responsibility to determine if impossible data should be stored in the DB (for example a date of 0000/00/00), or a record that requires a foreign key to a child table but doesn't include one on insert. It is up to the DB to reject with error data that is invalid. This ensures that no matter the source of the data, only well-formed and correct data will be stored. | |
| Jun 12, 2012 at 19:50 | history | answered | programmer | CC BY-SA 3.0 |