On Dec 12, 11:19 am, Roy Wright <[email protected]> wrote:
> 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...
Well, that was sort of my point. Putting a model under a module makes
sense when dealing with multiple databases, but merb doesn't handle
those situations as well as one (er, *I* at least) would expect. I
just use your suggestion of prepending the db name to the model class
name and that has worked fine. But I would like to know what "The"
correct way of handling a situation like that is.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
