> I'm assuming you have some additional query statements underneath the > session.delete() call, otherwise it wont throw an exception by itself > like that. The current policy with the Session is that after its > rolled back, you have to manually clean out whatever is wrong with it > - in this case "c" is still marked as deleted, so you'd need to > session.update(c) to "un-delete" it (or expunge() it). The next > release of SQLA will have some new transactional features for sessions > such that the "deleted" and "new" lists will be rolled back after a > rollback(), and all in-session instances will be expired...this kind > of thing is what we were sprinting on at Pycon.
Excelent!! That works perfect. I'm fascinated with your commitment. I can't believe that in just 9 minutes I have the solution... I'm extremely grateful to you. That new features of what are you talking are realy usefull. I'll be waiting... Thanks again... MarcosAlcazar Ps: Pycon it's a little far away for me. I live in Mendoza, Argentina... --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
