funny story, here's where it was added:
http://www.sqlalchemy.org/trac/ticket/1910 which is essentially your ticket !
:)
I just double checked and I had patched in rfde41d0e9f70
http://www.sqlalchemy.org/trac/changeset/fde41d0e9f70/. Is there
another commit that went against 1910? For
See http://www.sqlalchemy.org/trac/ticket/2372
--
You received this message because you are subscribed to the Google Groups
sqlalchemy group.
To post to this group, send email to sqlalchemy@googlegroups.com.
To unsubscribe from this group, send email to
sqlalchemy+unsubscr...@googlegroups.com.
Mike,
Old code:
==
def visit_bindparam(bindparam):
if bindparam.key in bind_to_col:
bindparam.value = lambda:
mapper._get_state_attr_by_column(
state, dict_,
Code wasn't covered and is a regresssion, fixed in rd6e321dc120d.
On Jan 10, 2012, at 10:58 AM, Kent wrote:
Mike,
Old code:
==
def visit_bindparam(bindparam):
if bindparam.key in bind_to_col:
Thank you very much!
On 1/10/2012 11:47 AM, Michael Bayer wrote:
Code wasn't covered and is a regresssion, fixed in rd6e321dc120d.
On Jan 10, 2012, at 10:58 AM, Kent wrote:
Mike,
Old code:
==
def visit_bindparam(bindparam):
i guess the patch is interacting with that load_on_pending stuff, which I
probably added for you also. It would be nice to really work up a new
SQLAlchemy feature: detached/transientobject loading document that really
describes what it is we're trying to do here.If you were to write
On Jan 9, 2012, at 2:30 PM, Kent wrote:
i guess the patch is interacting with that load_on_pending stuff, which I
probably added for you also. It would be nice to really work up a new
SQLAlchemy feature: detached/transientobject loading document that really
describes what it is we're
On 1/9/2012 2:33 PM, Michael Bayer wrote:
On Jan 9, 2012, at 2:30 PM, Kent wrote:
i guess the patch is interacting with that load_on_pending stuff, which I probably
added for you also. It would be nice to really work up a new SQLAlchemy feature:
detached/transientobject loading document
On Jan 9, 2012, at 2:36 PM, Kent Bower wrote:
that means some of the columns being linked to the foreign keys on the
target are None. If you want your lazyload to work all the attributes need
to be populated. If you're hitting the get committed thing, and the
attributes are only
On 1/9/2012 5:33 PM, Michael Bayer wrote:
On Jan 9, 2012, at 2:36 PM, Kent Bower wrote:
that means some of the columns being linked to the foreign keys on the target are None.
If you want your lazyload to work all the attributes need to be populated. If you're
hitting the get committed
On 12/27/2011 5:34 PM, Michael Bayer wrote:
On Dec 27, 2011, at 5:21 PM, Kent wrote:
So see what happens if you, for the moment, just monkeypatch over
orm.session._state_session to do a lookup in a global context if
state.session_id isn't set. If that solves the problem of I want
detached
On Dec 28, 2011, at 9:18 AM, Kent wrote:
Off topic, but from a shell prompt I sometimes find myself naturally
attempting this:
session.detach(instance)
and then when that fails, I remember:
session.expunge(instance)
I'm not asking for a change here, but quite curious: you think
On 2011-12-28 10:58 AM, Michael Bayer wrote:
detach(), also nice.
This seems most descriptive of what is actually taking place. I poured over the
docs for some time looking for the detach() method.
Michael
--
You received this message because you are subscribed to the Google Groups
On Dec 26, 5:12 pm, Michael Bayer mike...@zzzcomputing.com wrote:
On Dec 26, 2011, at 1:50 PM, Kent wrote:
Yes, a nice simplification.
I'm using it to lazyload attributes for objects that aren't in a
session. I'm not sure if you pointed me there, I think I found it
myself, but you
On Dec 27, 2011, at 8:10 AM, Kent wrote:
Sounds good, I'll look into that. But I'm curious why this approach
is preferable over the one I've currently got (callable_ seems more
public than _state_session).
callable_ does not accept the session as an argument, and while I looked into
So see what happens if you, for the moment, just monkeypatch over
orm.session._state_session to do a lookup in a global context if
state.session_id isn't set. If that solves the problem of I want detached
objects to load stuff, for you and everyone else who wants this feature,
then
On Dec 27, 2011, at 5:21 PM, Kent wrote:
So see what happens if you, for the moment, just monkeypatch over
orm.session._state_session to do a lookup in a global context if
state.session_id isn't set. If that solves the problem of I want detached
objects to load stuff, for you and
Yes, a nice simplification.
I'm using it to lazyload attributes for objects that aren't in a
session. I'm not sure if you pointed me there, I think I found it
myself, but you helped work out the later details...
Our app lives inside a webserver framework that, very appropriately,
in my opinion,
think I'll put:
state.session_id = None
in a finally block, but you get the idea
On Dec 26, 1:50 pm, Kent jkentbo...@gmail.com wrote:
Yes, a nice simplification.
I'm using it to lazyload attributes for objects that aren't in a
session. I'm not sure if you pointed me there, I think I found it
19 matches
Mail list logo
