On Apr 29, 2007, at 7:10 AM, Martin Aspeli wrote:
> Essentially, I'm dealing with a framework that has a storage layer > abstraction which is a little broken. It asks the storage to save > values > one-by-one, and there is no well-defined way to know when it's done > saving values. Previous attempts at SQL integration fell down on > things > like NOT NULL constraints, because they would essentially issue one > UPDATE statement for each column (well, an INSERT on the first one). im not sure what you mean by "it asks the storage to save one by one", if its just a matter of the schema design having circular-row relationships (i.e. cant just INSERT x and then INSERT y because they have foreign key constraints to each other), there is a relationship flag called "post_update" which is intended to make these possible. > > I guess what I'm after is a way to attach a "partial" object to a > session, and them modify it. I can see that working if SA doesn't > clone > objects in the session, i.e. my object references still point to the > thing in the session and SA doesn't attempt to validate the object as > soon as it's saved in the session. theres no cloning going on, you can flush() away any number of times. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
