[sqlalchemy] SQLAlchemy goes back to database when I wouldn't expect it to...

2010-02-08 Thread Kent
Consider a simple Order to OrderDetail relationship. Order's pk is orderid OrderDetail's composite pk is (orderid,lineid) A few questions follow output: o=Order() o.orderid = '0206001A134' #this order exists in the database line1=OrderDetail() #line exists in database line1.orderid

Re: [sqlalchemy] SQLAlchemy goes back to database when I wouldn't expect it to...

2010-02-08 Thread Michael Bayer
On Feb 8, 2010, at 4:12 PM, Kent wrote: Ok, here are my questions: a) The merge eagerloads the order, along with its lines, but then, directly afterward, issues two additional SELECT statements for the two lines, even though these were already eagerly-loaded. That surprised me. Why is