On Dec 28, 2007, at 5:50 AM, Denis S. Otkidach wrote:
> Sure, I can get an object from DB and copy data from new one. But > there is a lot of object types, so have to invent yet another meta > description for it (while it already exists in sqlalchemy). And > requirements changes often, so I have to change scheme in 2 places. > This is not good and error prone. Why I have to invent new description > when there is already one from sqlalchemy mapping? Can't I use it for > my purpose? Something like merge(objFromDB, newObj) will solve the > problem. session.merge() does copy the attributes of one object into another. theres some bugs with dont_load that have been fixed in trunk so try out the trunk if you have problems. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
