3 ms·
but the database is often a red-headed stepchild that doesn't get the attention it deserves On my last three major projects, I have committed to devoting the p
by MartinCron 15y ago
but the database is often a red-headed stepchild that doesn't get the attention it deserves
On my last three major projects, I have committed to devoting the proper level of attention to the database, with automatically building databases in some environments, scripted scheme changes and seed data loading as part of the mainline code base, etc. and I have found the difference to be immense in practical terms. I can move more quickly, more safely, and have a better quality of life as a developer.
One of the best returns on (effort) invested I have ever seen.
- lukencode 15y agoI definitely agree. We have been using fluent migrator (https://github.com/schambers/fluentmigrator https://github.com/schambers/fluentmigrator) for our .net based projects at work for database migrations and versioning
- MartinCron 15y agoThanks. Fluent Migrator looks pretty cool. I've been rolling my own stuff as-needed. As a result, it has evolved into something pretty useful for the problems I've encountered so far, but does nothing outside of what I've already thought of. I can see using the migrator as a good jumping off point.