Re: ActiveRecord: private versus protected methods

Urbanus, that is exactly what I'm doing right now. I'm packaging it as a generic, wide audience plugin called Migration Extensions. I haven't been troubled by private methods, though.

It's a shame we're building the same thing separately... Tell me if you're interested to see, next week when I'm going to have something concrete in alpha state I can share it with you.

On 9/28/06, urbanus <urbanus@xxxxxxxxx> wrote:

I'm considering a fairly deep change to the way migrations work.  I'm
looking at adding a *namespace* to migrations, so when doing a
migration you would specify the name and version number for the
required migration.

This would allow you to deploy parts of Rails apps as a kind of
plug-in.  So when you migrate up or down, you can specify which part of
the database you're referring to.

--~--~---------~--~----~------------~-------~--~----~
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 rubyonrails-core@xxxxxxxxxxxxxxxx 
 To unsubscribe from this group, send email to rubyonrails-core-unsubscribe@xxxxxxxxxxxxxxxx 
 For more options, visit this group at http://groups.google.com/group/rubyonrails-core 
 -~----------~----~----~----~------~----~------~--~---