Delete operation: Does it cascade, or leave orphans?

ddumas

I am hesitant to use the delete operation on objects that have "children". Ex. attibutes that "allow multiple".

Is there any way to either specify DELETE CASCADE, similar to a database, or conversely, gaurd against a delete which can leave orphan instances?

I know I can code my delete operation to call a process, and check all this stuff manually, but that would be allot of extra work if AwareIM already has a way to do this.

nlarson

if the reference is Owned By a parent delete will delete the children. If it is peer or owner of they get left.

ddumas

nlarson wrote
if the reference is Owned By a parent delete will delete the children. If it is peer or owner of they get left.

Thanks. Sounds like I will need to code my own process to protect against that behavior. Do not want an inadvertent delete to cause deletes by accident. Also, do not want to leave orphans on an intentional delete.

It would be great if awareIM had an object checkbox controlling the behavior of this.

nlarson

I had the same worry so I created a 'Recycling Bin'. My Delete Button, just changes a value in the data which hides it from most queries. Admins have a function to review and delete.

Another approch might be to read protect for all but an admin.

ddumas

nlarson wrote
I had the same worry so I created a 'Recycling Bin'. My Delete Button, just changes a value in the data which hides it from most queries. Admins have a function to review and delete.

Another approch might be to read protect for all but an admin.

That's a good idea - a "deleted flag" of sorts.