There's also the issue of models referenced from within migrations
where you might want to explicitly specify a module hierarchy that
does not match the model's actual namespace.
Perhaps we can include a method that allows you explicitly set the sti
class name?
class SomeMigration < ActiveRecord::Migration
class User < ActiveRecord::Base
end
class Administrator < User
sti_class_name 'CustomNamespace::Administrator'
end
end
On Mon, May 5, 2008 at 7:43 AM, Rodrigo Kochenburger <[EMAIL PROTECTED]> wrote:
>
> @Koz
>
> Yeah, i've added the configuration option in order to allow back
> compatibility.
>
> Also, i've moved the ticket to lighthouse
>
> http://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/114-namespaced-models-and-sti
>
> Cheers
>
>
>
> On May 3, 10:56 pm, "Michael Koziarski" <[EMAIL PROTECTED]> wrote:
> > > Yeah, definitely.
> > > Can i count with your +1 for this patch? :)
> >
> > My only concern with this kind of change is what happens to existing
> > data that's stored in the database.
> >
> > I see the option to turn this behaviour off, is that only needed for
> > backwards compatibility reasons? Are there any other downsides to the
> > change?
> >
> > Finally, if you could move this to lighthouse it'd make the reviewing
> > a little easier.
> >
> > --
> > Cheers
> >
> > Koz
> >
>
--~--~---------~--~----~------------~-------~--~----~
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@googlegroups.com
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
-~----------~----~----~----~------~----~------~--~---
