> This leads me to another scenario. Namespaced models.... quite simply > as it stands you can in /app/models/ make a folder called /customer/ > there add tag.rb and note.rb. With models Customer::Tag and > Customer::Note. One thing is the table_name will remain "tags" and > "notes", which in this case should be prefixed by the namespace name > like "customer_tags" and "customer_notes". Also with the ability to > have a root model like Customer in /customer/root.rb.
On a totally unrelated note, I'm completely against the idea of namespaced models. Putting them in a separate directory is perfect, but not naming them like Customer::Tag. Why would u need to do that ? -Pratik -- http://m.onkey.org --~--~---------~--~----~------------~-------~--~----~ 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 [email protected] 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 -~----------~----~----~----~------~----~------~--~---
