4 ms·
Actually even senior developers or architects make mistakes. Philosophy grad or not, it doesn't matter. That's to be expected. What's more questionable is: *
by eloisant 14y ago
Actually even senior developers or architects make mistakes. Philosophy grad or not, it doesn't matter. That's to be expected.
What's more questionable is:
* Developers have access to the production database from their machine, while it should only be accessible to the front machines within the datacenter.
* Junior developers don't need an access to production machine, only sysops and maybe the technical PM.
* No backup of the production database. WTF???
If they had a hardware failure they would have been in the same shit.
- fusiongyro 14y agoIt's a nice theory, but not everybody has that much staff. You can get by with proper backups and running against local copies of production.
- Qantourisc 14y agoConstrains also act like bug protections. If you screw up your database tells you right away, and not a beta tester much later.
- fusiongyro 14y agoYou're preaching to the choir. :)
- mbell 14y agoI'll add another one: * No Foreign Keys Attempting to clear the table should have just thrown a constraint violation error.
- jasonswett 14y agoExactly!!!!
- eloisant 14y agoWell, depending how you configure your cascade clearing the user table could have cleared all the other tables also :) "on delete cascade"!
- mbell 14y agoTrue on MySql with InnoDB, wouldn't be true with postgres. You'd have to use TRUNCATE CASCADE on postgres to avoid the foreign key error.