Object is already deleted
(Adding message template to the top of the page)
No edit summary
 
(2 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{message|Write the content here to display this box}}
<message>Write the content here to display this box</message>
If you get the error message <code>"Object is already deleted"</code> in the client or in logs, your EAL is trying to delete an object that has already been deleted.
If you get the error message <code><span class="col-black">'''"Object is already deleted"'''</span></code> in the client or in logs, your EAL is trying to delete an object that has already been deleted.


How can one even try to delete a deleted object? An object in an ECO space is not removed from the ECO space until it's saved. Until then, the object is still there and can be accessed through an earlier obtained reference.
How can one even try to delete a deleted object? An object in an ECO space is not removed from the ECO space until it's saved. Until then, the object is still there and can be accessed through an earlier obtained reference.
Line 6: Line 6:
Do something like this to avoid such a situation:
Do something like this to avoid such a situation:
  object.existing.whenTrue(object.delete)
  object.existing.whenTrue(object.delete)
See also: [[OCLOperators existing]]
'''See also:''' [[Documentation:OCLOperators existing|OCLOperators existing]]
[[Category:OCL]]
[[Category:OCL]]
{{Edited|July|12|2024}}
{{Edited|July|12|2025}}

Latest revision as of 05:31, 11 February 2025

This page was created by Lars.olofsson@mdriven.net on 2022-12-28. Last edited by Stephanie@mdriven.net on 2025-02-11.

If you get the error message "Object is already deleted" in the client or in logs, your EAL is trying to delete an object that has already been deleted.

How can one even try to delete a deleted object? An object in an ECO space is not removed from the ECO space until it's saved. Until then, the object is still there and can be accessed through an earlier obtained reference.

Do something like this to avoid such a situation:

object.existing.whenTrue(object.delete)

See also: OCLOperators existing