we have a bunch of folks who are very opposed to anything "global" at
all. SA 0.2 abstracts the Engine away from the Table by using a
MetaData object, which is just a collection of Table objects, and may
or may not be connected to an Engine. an available subclass of
MetaData is DynamicMe
Qvx wrote:
"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 possi
On 4/23/06, Jonathan LaCour <[EMAIL PROTECTED]> wrote:
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 imp
3 matches
Mail list logo
