Re: ActiveRecord: private versus protected methods

Hi Jeremy,

> You need protected only if you wish the call the method from a subclass. The

Exactly.  That's the issue.

> inherited public method is not affected. Please bring up specific examples
> (preferably as Trac tickets) and we will address them.

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.

For example, you might have a Rails app called "portal" that provides
all the core functionality of your website, into which you can add
optional plug-ins such as "cms", "discussion_board", etc.  Each of
those plug-ins would have their own database requirements, in addition
to the main "portal".

I'm also looking at dependencies between the parts, e.g. "cms" version
4 might depend on "portal" version 2 or above.

Rails migrations almost do what I need; except that you can't put
different sorts of migrations into the one Rails database (AFAIK).

I could do all this using the existing migration classes as a basis if
-- as discussed previously -- I could sub-class them and override their
public methods.  But I can't, because the public methods rely on
private methods.

Thanks,
Urbanus


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