Jesus, gah. And I thought the name sounds "home-ish" – the party was great, too bad I had to leave early. But I'll take Michael up on the offer and try to come over for working at your place for a day or so soonish.
PS: You're now officially added to my "List of People to Bug About merb Directly", btw. ;o) (First I'll have to make lepilo work by monday evening, and after that I'll do more refactoring which includes the namespacing and slicing up) On Dec 12, 7:45 pm, "Martin Gamsjaeger" <[email protected]> wrote: > Hey Samo, > > Even with these minor CSS3 selector issues, it's fairly easy to work > with namespaced models in merb, you shouldn't encounter too many > problems I guess. > > By the way, did you like our office warming party? (I'm one of the > guys in Gesellenhausstr. Linz, quasipartikel office :) > > cheers > snusnu > > On Fri, Dec 12, 2008 at 19:37, Samo Korosec <[email protected]> wrote: > > > Sorry to the original poster for not being able to offer any advice, > > but I would, too, at some point like to move my current merb project > > into a slice and with that, if possible, namespace my models. Since > > they use quite generic names I don't want anyone who'd use them to > > have to think about possible name clashing, or having to split up the > > page in two databases, either. > > > Actually I thought it should be easily doable, and I haven't even > > considered the CSS issues it would bring. :-/ > > > On Dec 12, 11:08 am, jonuts <[email protected]> wrote: > >> 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 -~----------~----~----~----~------~----~------~--~---
