I hadn't planned any future 0.5 releases, 0.7 is almost ready for betas.  What 
are the incompatibilities you have with 0.6 ?


On Dec 7, 2010, at 11:58 AM, Ralph Heinkel wrote:

> This would be great! Thanks, Michael!
> 
> (is this also going into the 0.5.x branch - we are not yet able to
> upgrade to 0.6.x due to incompatibilities...)
> 
> Ralph
> 
> On Dec 7, 4:09 pm, Michael Bayer <[email protected]> wrote:
>> when I answered your email I realized we should probably add a "bind" 
>> argument to connection() and execute(), for those cases where you have the 
>> actual "bind" (and the kw, for subclass situations).     ticket #1996
>> 
>> On Dec 7, 2010, at 7:32 AM, Ralph Heinkel wrote:
>> 
>>> Hi Michael,
>> 
>>> thanks for your help.
>>> Since some of my engines are not bound to mappers I've tried the
>>> approach suggested in your previous post to subclass Session so that
>>> 'get_bind' would accept an additional 'engine' argument. This works
>>> fine with Session.execute() which passes **kw down to the 'get_bind'
>>> method, but unfortunately Session.connection() doesn't. Is this
>>> omitted intentionally, or could it be added?
>> 
>>> Thanks a lot,
>> 
>>> Ralph
>> 
>>>> Here you'd use Session.execute() and Session.connection() to get at the 
>>>> Connection you'd normally get from engine.contextual_connect() 
>>>> (http://www.sqlalchemy.org/docs/orm/session.html#using-sql-expressions...) 
>>>> .    execute() and connection() accept a "mapper" argument for the case 
>>>> where individual engines are associated with individual mappers, and both 
>>>> ultimately call get_bind() which you can override via subclass if desired 
>>>> to accept other kinds of arguments.
>> 
>>> --
>>> You received this message because you are subscribed to the Google Groups 
>>> "sqlalchemy" group.
>>> To post to this group, send email to [email protected].
>>> To unsubscribe from this group, send email to 
>>> [email protected].
>>> For more options, visit this group 
>>> athttp://groups.google.com/group/sqlalchemy?hl=en.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "sqlalchemy" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to 
> [email protected].
> For more options, visit this group at 
> http://groups.google.com/group/sqlalchemy?hl=en.
> 

-- 
You received this message because you are subscribed to the Google Groups 
"sqlalchemy" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/sqlalchemy?hl=en.

Reply via email to