Comments on: Using Multiple Databases in TurboGears 2

By: Jorge Vargas

Jorge Vargas — Wed, 29 Jul 2009 22:04:01 +0000

@Richard actually that’s wrong. This is not a hack TG2 is build to support multiple DBs, sqlalchemy has done so pretty much since day one. That is totally different from the “django ORM”

The subclass is needed for convenience and it is indeed coming. I know for sure this will land into 2.1 and I’m part of the core team.

By: Jorge Vargas

Jorge Vargas — Wed, 29 Jul 2009 22:04:00 +0000

@Richard actually that’s wrong. This is not a hack TG2 is build to support multiple DBs, sqlalchemy has done so pretty much since day one. That is totally different from the “django ORM”

The subclass is needed for convenience and it is indeed coming. I know for sure this will land into 2.1 and I’m part of the core team.

By: Laurin

Laurin — Fri, 17 Jul 2009 15:18:24 +0000

This is very good information – thanks for sharing.

I’m going to add some of this to my application in turbogears, to replace an old way I was connecting to multiple legacy databases.

I may even try elpargo’s suggestion to iterate over keys to handle the case where I may add an additional database as needed.

Cheers, Laurin

By: Laurin

Laurin — Fri, 17 Jul 2009 15:18:00 +0000

This is very good information – thanks for sharing.

I’m going to add some of this to my application in turbogears, to replace an old way I was connecting to multiple legacy databases.

I may even try elpargo’s suggestion to iterate over keys to handle the case where I may add an additional database as needed.

Cheers, Laurin

By: Richard Cooke

Richard Cooke — Wed, 15 Jul 2009 15:17:31 +0000

Hah! Nice to know I’m not alone. I’m trying to choose between Django 1.0 and TG2.

Similar problem. We want to make user web pages to access our legacy DBs.

Django has a hack for multiple Dbs. Similar in type to what you do here.

The only thing that is making me choose Django (at least for now) is that I know the DEV branch is working on it. In fact, they hope to finish it up this summer with GSOC. Which means it could be rolled into Trunk in January.

So, I “know” its coming. Whereas, with TG2 it seems to be more of a question mark.

Thanks for the post!

By: Richard Cooke

Richard Cooke — Wed, 15 Jul 2009 15:17:00 +0000

Hah! Nice to know I’m not alone. I’m trying to choose between Django 1.0 and TG2.

Similar problem. We want to make user web pages to access our legacy DBs.

Django has a hack for multiple Dbs. Similar in type to what you do here.

So, I “know” its coming. Whereas, with TG2 it seems to be more of a question mark.

Thanks for the post!

By: Celil

Celil — Fri, 10 Jul 2009 05:19:42 +0000

Is it possible to load databases whose name will be determined during runtime, i.e. without having to add their names to the config file?

By: Celil

Celil — Fri, 10 Jul 2009 05:19:00 +0000

Is it possible to load databases whose name will be determined during runtime, i.e. without having to add their names to the config file?

By: Jorge Vargas

Jorge Vargas — Thu, 25 Jun 2009 01:36:58 +0000

Nice post thank you.

I think this can be improved in two ways
1- I believe you can use just one “maker” instance.
2- setup_sqlalchemy could be made to iterate over the keys.

hit me up on IRC, if you can come on Saturday for the bugfix day we can get this in.

Regards elpargo.

By: Jorge Vargas

Jorge Vargas — Thu, 25 Jun 2009 01:36:00 +0000

Nice post thank you.

I think this can be improved in two ways
1- I believe you can use just one “maker” instance.
2- setup_sqlalchemy could be made to iterate over the keys.

hit me up on IRC, if you can come on Saturday for the bugfix day we can get this in.

Regards elpargo.