/explore
|
You are here 
|
blog.pchudzik.com | ||
| | | | |
www.leerichardson.com
|
|
| | | | | A blog about dev: web and mobile, especially .Net, OSS and CI. | |
| | | | |
andyatkinson.com
|
|
| | | | | This month's PGSQL Phriday topic prompts writers to discuss how their team manages PostgreSQL database schema changes. | |
| | | | |
blog.julik.nl
|
|
| | | | | We get attached to code - sometimes to a fault. Old migrations are exactly that. They're digital hoarding at its finest, cluttering up your codebase with files that serve absolutely no purpose other than to make you feel like you're preserving some kind of historical record. But here's the brutal truth: your old migrations are utterly useless. They're worse than useless - they're actively harmful. They're taking up space, they are confusing (both for you and new developers on the project), and they give you a false sense of security about your database's evolution. If your database is out-of-sync with schema.rb you need to solve that problem anyway, and - if anything - the migrations make that problem worse. | |
| | | | |
curatedsql.com
|
|
| | | |||
