before v3463, _state was a property and was setup on the fly whenever used. now its being setup into the __init__-replacement of the object.
Thus, with the property it was possible as side-effect to have an object instance _before_ having any sqlalchemy around, then declare/build mappers/ whatever, and then save /use that instance as db-persistent. Now this wont work, as the instance has no _state attribute, and noone to set it up. i guess this usage case - of instances having wider lifetime than orm-mapping itself - is rare. i use it for tests, running many db- tests over same instances. So i'll probably put a check in my save() method to setup that missing ._state. Not sure about the mapext.init_instance(), and why's that is called before the original oldinit, and is given that oldinit as argument. Anyway it would be nice if these lifetime-related expectations/limitations are documented somewhere. Another one is the ._instance_key that stays on the instance after orm is gone (the ._state will also stay). ciao svilen --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
