On second thought, i may be able to get access to the mappers using
the engine as an identifier.  Give me a day or two and this problem
may resolve itself.

Sorry for the re-hash guys.

-chris

On Dec 17, 8:48 am, percious <[email protected]> wrote:
> The metadata needs to be known because the metadata contains the
> mapping which associates the table to the objects.
>
> Catwalk2 already supports multiple databases.  I run it with 4
> instances in my current implementation.
>
> cheers.
> -chris
>
> On Dec 17, 7:44 am, John M Camara <[email protected]> wrote:
>
> > On Dec 16, 11:47 pm, percious <[email protected]> wrote:
>
> > > Hey guys.
>
> > > I'd like to add the following to the init_model() function in mode/
> > > __init__.py in the default template:
>
> > > metadata.bind = engine
>
> > > This is to allow dbsprockets (catwalk2) to have access to the bound
> > > metadata.  Without this change, those two items will not work out of
> > > the box.
>
> > > cheers.
> > > -chris
>
> > Chris,
>
> > Why don't you pass the engine when you bind dbsprokets to the
> > controller.  Doing it this way allows for multiple instances of
> > dbspockets and thus support multiple databases.  With the above, your
> > kinda of limited to one database in the app that gets to take
> > advantage of dbsprokets.
>
> > John
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TurboGears Trunk" 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/turbogears-trunk?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to