In http://www.sqlalchemy.org/trac/changeset/7025%3A0a6576abea5b#file1
you added a warning that I'm hitting now.
'when save-update cascade is disabled, or the target object is
otherwise not
present in the session, and collection/scalar changes have taken
place. A warning
is emitted describing the
On Dec 27, 2011, at 1:51 PM, Kent wrote:
In http://www.sqlalchemy.org/trac/changeset/7025%3A0a6576abea5b#file1
you added a warning that I'm hitting now.
'when save-update cascade is disabled, or the target object is
otherwise not
present in the session, and collection/scalar changes have
On 12/27/2011 2:34 PM, Michael Bayer wrote:
On Dec 27, 2011, at 1:51 PM, Kent wrote:
In http://www.sqlalchemy.org/trac/changeset/7025%3A0a6576abea5b#file1
you added a warning that I'm hitting now.
'when save-update cascade is disabled, or the target object is
otherwise not
present in the
On Dec 27, 2011, at 3:33 PM, Kent wrote:
Haha! I sense you're getting irritated, Mike!
oops...that should never show...
There are certain objects that aren't placed in the session because they
aren't in the merge cascade (purposefully). These are transient objects
I think that's