ManyToMany and OneToMany don't know about their "fields" until touched #1018

nafg opened this Issue May 20, 2011 · 3 comments

2 participants


See e.g. -- if you load a OneToMany from the database and call delete_!, the MappedOneToMany's children won't be deleted (even if you mixed in Cascade) because objects are lazily initialized. Initialize MappedOneToMany and MappedManyToMany when running reflection to discover MappedFields.


(In [[r:f51d88425dba92c37b1b6463b408bf633fb5843c]]) Fix #1018

Branch: wip_1018


(In [[r:2816e53c3158dddbd0f8ef93f6c825a147f78a25]]) Fix #1018

Branch: master

@nafg nafg was assigned Mar 1, 2012
@nafg nafg removed their assignment Apr 7, 2014
@etorreborre etorreborre pushed a commit to etorreborre/framework that referenced this issue Dec 3, 2014
@nafg nafg Fix #1018 2816e53
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment