I cannot help but believe that matters are headed in exactly the wrong direction. We already have a serious problem (as discussed in AWDR) with the asynchronous relationship between code and the current migration level. Now there is talk about creating ANOTHER asynchronous set of tasks which depends on both code and migration?
The creation of an administrative user is very tightly bound to the creating of the users table. Separating them looks unnatural, difficult, and errorprone to me. I expect that there are similar situations in other circumstances. -- I'm confused DHH's statements regarding the transitory nature of migrations. Is there a best practices document someplace that explains the matter? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
