Hi,
SAContext is a SQLAlchemy front end that organizes your engines,
metadatas, and sessions into one convenient object, while still
allowing access to the underlying objects for advanced use.
Mike, this looks like good work and something that is needed. I notice
for instance that the
Hi,
SAContext is strictly a configurational object, it doesnt add any new
I see. I had wondered if this was WSGI middleware that took care of
database transactions (as has been mooted in the TG area recently).
Obviously as a config object, it can't do either of the things I suggested.
Well I would prefer not using None and rather making the user pass the
correct key, so that way default become no different they using any other
key and users could just as simply call their key main or what ever else
turns them on. Assuming that they use the correct syntax in the ini file
On Wednesday 11 July 2007 21:49:48 Mike Orr wrote:
On 7/11/07, Jose Galvez [EMAIL PROTECTED] wrote:
Dear Mike,
I've read the doc string in the new sacontext and was just
wondering why for add_engine_from_config do you have to
explicitly pass None for the default connection? it would make
I've just reread the sacontext doc string and realize that what I've said
really does not make any sense. To go back a step I would advocate using
default rather then None
Jose
On 7/11/07, Jose Galvez [EMAIL PROTECTED] wrote:
Well I would prefer not using None and rather making the user pass
On 7/11/07, Mike Orr [EMAIL PROTECTED] wrote:
On 7/11/07, Jose Galvez [EMAIL PROTECTED] wrote:
Dear Mike,
I've read the doc string in the new sacontext and was just wondering why for
add_engine_from_config do you have to explicitly pass None for the default
connection? it would make more
On Jul 11, 2007, at 2:49 PM, Mike Orr wrote:
It is awkward but Python has no other built-in value for default.
Using a string means people may spell it differently, and the
.metadata and .engine properties require a fixed value. Making it
optional means the second positional argument
