| Hi all, I submitted a patch the other day for an issue I ran into running an "add_column" migration on a sqlite3 database when there is existing data in the table, and the new column has ":null=>false". Details at http://dev.rubyonrails.org/ticket/5215. The issue I encountered was not picked due to the unit test not having any actual data in it before running the migration. I later ran into an issue with postgresql when doing an "add_column" migration for a different reason. I am wondering two things: 1) What's the normal period from when a patch is submitted to when it is reviewed or committed? 2) if #1 happens, my patch to the unit test might reveal bugs in other adapters besides sqlite3, so how would that be handled? I really like the idea of migrations and would love to see the stability of them improved. Thanks, Greg |
_______________________________________________ Rails-core mailing list Rails-core@lists.rubyonrails.org http://lists.rubyonrails.org/mailman/listinfo/rails-core
