Originally reported by: Michael Bayer (Bitbucket: zzzeek, GitHub: zzzeek)
when post_update does the second UPDATE statement, it updates all columns that were already inserted. it should be modified to update only those columns that were affected by the ClauseSynchronizer used by the post_updated property. mapper should get a separate function for post_update since its somewhat different from save_obj/delete_obj.
the unittests in cycles.py use tables that have only the foreign keys and should have some extra "data" columns put in there to test this.
Originally reported by: Michael Bayer (Bitbucket: zzzeek, GitHub: zzzeek)
when post_update does the second UPDATE statement, it updates all columns that were already inserted. it should be modified to update only those columns that were affected by the ClauseSynchronizer used by the post_updated property. mapper should get a separate function for
post_update
since its somewhat different fromsave_obj
/delete_obj
.the unittests in cycles.py use tables that have only the foreign keys and should have some extra "data" columns put in there to test this.