Re: [sqlalchemy] unexpected behavior with the orm

2013-04-02 Thread Michael Merickel
Mike, thanks for the clarification. I never noticed that particular implication of the default cascade! On Mon, Apr 1, 2013 at 1:23 PM, Michael Bayer wrote: > > On Apr 1, 2013, at 2:10 PM, Michael Merickel wrote: > > > I ran into a situation the other day where I would create a new object > but

Re: [sqlalchemy] unexpected behavior with the orm

2013-04-01 Thread Michael Bayer
On Apr 1, 2013, at 2:10 PM, Michael Merickel wrote: > I ran into a situation the other day where I would create a new object but > copy over some properties from an earlier version of the object. To do this, > I first created the new object, then I queried the database for the latest > copy o

[sqlalchemy] unexpected behavior with the orm

2013-04-01 Thread Michael Merickel
I ran into a situation the other day where I would create a new object but copy over some properties from an earlier version of the object. To do this, I first created the new object, then I queried the database for the latest copy of the object, copied properties to the new object, then added