Re: ActiveRecord: private versus protected methods

On Wed, Sep 27, 2006 at 07:48:29PM -0700, urbanus wrote:
> Rails migrations almost do what I need; except that you can't put
> different sorts of migrations into the one Rails database (AFAIK).

A couple of guys at a client of mine implemented this, and it involved
opening up one method to the outside world to specify the name of the
schema_info table (we used schema_info_<name> for the different parts).  It
was quite small and simple.  They didn't subclass, but as Koz mentioned
private methods don't necessarily preclude subclassing.

The other stuff you're talking about (schema chunk dependencies) would be
trickier, but I'd be inclined to leave that to application-level
dependencies (surely you're going to need code to go along with those
schemas, so tying it all up into a single version number thing would be
pretty clean).

- Matt

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---