Ticket #1717 (closed defect: fixed)
[PATCH] Cannot separate savisit into its own database
|Reported by:||toshio||Owned by:||anonymous|
According to #1238 having visit in a separate database from the application database is supposed to work under SQLAlchemy. This is not yet correct. The problem is that the get_engine() call only returns the database configured in the application's configuration file while the table could actually be created in a different database (as documented at http://docs.turbogears.org/1.0/SQLAlchemy). I needed to apply the attached patch to get this to work.