This repository is private.
All pages are served over SSL and all pushing and pulling is done over SSH.
No one may fork, clone, or view it unless they are added as a member.
Every repository with this icon (
) is private.
Every repository with this icon (
This repository is public.
Anyone may fork, clone, or view it.
Every repository with this icon (
) is public.
Every repository with this icon (
commit bca8751e40a5594c4de2ca58e089b8d98e44632b
tree 34a89b57cdf2ac2092c103975eeb2fa0f51c03e8
parent 2d372d704987e05712ccd937e78d8dbd41242efe
tree 34a89b57cdf2ac2092c103975eeb2fa0f51c03e8
parent 2d372d704987e05712ccd937e78d8dbd41242efe
... |
... |
|
... |
... |
|
... |
... |
|





Comments
What about the common technique of future-proofing migrations by defining the class being migrated within the namespace of the migration itself?
The solution could be as simple as adding a sti_class_name method on ActiveRecord::Base, cleaning up the repetition of all the store_full_sti_class ? self.class.name :
@duncanbeevers
I’m planning to address this issue and some others asap.
I’ll try to solve every issue listed in the ticket1, so if there is anything else please post there.
[1] http://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/114-namespaced-models-and-sti