title: Why is there no foreignAutoDelete?
body: <p>I'm using Ormlite for Android to convert an existing application from file to database storage of objects. I have a fairly complex object data structure which I need to get into the database and initially at least I don't want to modify too much of the object structure to accomplish this. In this existing structure I have quite a few levels of nested foreign objects.</p>
  
  <p>My question, foreignAutoCreate seems to work pretty well automagically. When I create an object in the database that has foreign objects, that themselves have foreign objects, etc. down to four or five levels, the single create for the master containing object populates all the foreign objects down to all these levels.</p>
  
  <p>I do not believe there is a way to delete the master object and have ormlite cascade the deletes down through all the levels of contained foreign objects.   I want to confirm that I'm not missing something and there's not an easier solution for what I'm doing, which is using triggers to delete everything upon a delete from the master table.  I understand that cascade deletes are an option, though I could not get it to work. But even if it did work I'm still wondering about the absence of a foreignAutoDelete option as having some of the configuration in the database and some in ormlite seems like it may eventually cause problems.</p>
  
  <p>Right now I'm having problems completing an update option through all these levels of foreign objects.  Initially, I was creating the master object and it would create all the children.  I would try to update the master object or delete and then readd the master object however it did not seem to impact the children (they were not updated).  After adding cascade deletes, I assumed that deleting the master object and cascading through its children and then readding the master object would effectuate the "update", however right now the children aren't being added back when I readd the master object.  I'm thinking there's some timing/transaction issue with the delete triggers on child tables happening after adding back the master object.  The foreignAutoCreate remains on for all the child objects so I'm assuming they should be populated on the second creation of the master object after everything has been cleared out of the database.</p>
  
  <p>Hope the question makes sense and thanks in advance for any responses.</p>