3 ms·
So you want to implement a new feature, and test it locally, then run tests to make sure you didn't break anything, and when you are done, upload the changes to
by z3t4 10y ago
So you want to implement a new feature, and test it locally, then run tests to make sure you didn't break anything, and when you are done, upload the changes to the production server. This is sane devops, nothing fancy, yet impossible with todays databases. You basically have to manually do the same changes you did in development to the production database, then test if it works on live data in production. Then your finger might slip when writing an SQL query and you have to reset all production data from backup.
- majewsky 10y agoI for one would not let developers access ny production databases when they clearly don't have any idea how to copy a snapshot into the QA database.
- z3t4 10y agoMay I ask how much it would cost, in total man hours, to for example change the name of a field ? For example make "name" into firstName and lastName.
- majewsky 10y agoAnywhere between maybe 1-2 man hours and multiple man months, depending on how nice the data is right now, and how accurate it need to be split. The optimal case would be the application already enforcing values to look like e.g. "last, first", so that the migration can happen via a simple regex.