jonuts wrote: > Can you explain to me the benefits of namespacing your models? I have > been trying to figure it out for a long time now, and I can't see why > you would need it. If a model is just a representation of a database > table, it needs a unique name anyway. Unless merb treats a namespaced > model as a separate repository (which it doesn't, but would be pretty > cool), or namespacing serves some purpose for an ORM that I have never > used, I really don't understand what benefits namespacing brings you.
I wrote a rails app a while back that connected 5 legacy databases (total 273 tables). There were a couple of tables with identical names in different databases. I used a namespace for each database, which worked well except for a couple of external tools I tried that just didn't handle namespaces. If I was to do it again, I'd probably just name my models by prepending the database name to the table name and forgo namespaces. Just my 2 cents... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "merb" 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/merb?hl=en -~----------~----~----~----~------~----~------~--~---
