> Well as long as you want to be able to load data and perform updates on > Instance.name using normal ORM patterns, you'd still have that column > mapped, if you want to put extra things into it to signal your migration > tool, there is an .info dictionary available on the Column that you can > use to do that. A function like "removed_field()" can certainly wrap > around a normal column mapping and populate a hint into the .info > dictionary that online migrations will pick up on.
I intentionally didn't (try to) define RemovedField because I figured it might contain some nasty proxy bits to make it continue to work. However, glad to hear that there is already a provision here that we can use -- that sounds perfect. --Dan __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev