Explore >> Select a destination
|
You are here 
|
vsevolod.net | ||
| | | | |
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. | |
| | | | |
quanttype.net
|
|
| | | | | A database schema migration tool has three tasks: creating, managing, and executing migrations. | |
| | | | |
www.vintasoftware.com
|
|
| | | | | Learn essential Django migration best practices to maintain database consistency. Discover how to properly manage schema changes and avoid common pitfalls in your applications. | |
| | | | |
janko.io
|
|
| | | In this tutorial, we'll show how to add fully functional authentication and account management functionality into a Rails app, using the Rodauth authentication framework. Rodauth has many advantages over the mainstream alternatives such as Devise, Sorcery, Clearance, and Authlogic, see my previous article for an introduction. | ||
