Also, I moved ActiveMapper to always use the default engine, as there
were a lot of hacks inside ActiveMapper to allow for engine swapping. The
use of the default engine and the "global_connect" functionality
significantly improves the usability of ActiveMapper.
"global" part from global_connect name just raised an alarm signal inside my head. If I'm reading you correct, global_connect will make it impossible to use more than one database. I hope I'm missing something obvious.
What is wrong with __engine__ module variable?
If it is possible to still connect to different database per python module then I guess I'm OK with global_connect. Just give me a recipe how to connect to different database in each module and I'll be happy.
