yes a few change names, reconstruct_instance, init_instance, init_failed. On Dec 24, 2011, at 7:42 PM, Kent Bower wrote:
> Right. And reconstruct_instance() was renamed load()? > > On 12/24/2011 5:56 PM, Michael Bayer wrote: >> On Dec 24, 2011, at 10:04 AM, Kent wrote: >> >>> As the migration guide suggests, I'd like to embrace the events API. >>> Is mapper event load() invoked at exactly the same place as the >>> deprecated reconstruct_instance() ? >> yeah nothing has been moved. All the places where the internals would call >> XXXExtension.xxx_event() were just replaced with self.dispatch.xxx_event(), >> and the old Extension classes are invoked via an adapter to the new system. >> All unit tests for the extension system remain in place and haven't been >> modified. >> >> >> >>> -- >>> 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 >>> sqlalchemy+unsubscr...@googlegroups.com. >>> For more options, visit this group at >>> http://groups.google.com/group/sqlalchemy?hl=en. >>> > > -- > 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 > sqlalchemy+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/sqlalchemy?hl=en. > -- 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 sqlalchemy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
