Delete in IUpdate (deleteObjects)

[jburel]

The update service has a deleteObjects method.
This should probably be reviewed as part of the delete effort

[jburel]

Mark: we can probably close that ticket.

[mtbcarroll]

There is an undocumented deleteObject that seems to simply use the Hibernate session method for deleting objects. I don't know if this is API we actually want to offer, or deprecate? If no changes needed here, sure happy to close.

[mtbcarroll]

Ah, Jean-Marie explains that it's useful for a quick synchronous deletion of ILinks. Perhaps I should add some documentation.

[jamoore]

It's possible to pass any class to DeleteI2? That would be the prereq for deprecating/removing this. It's probably used most often for unlinking.

[mtbcarroll]

Yes, deleting links should be pretty quick through Delete2I. If we would prefer to deprecate, then I could switch the implementation to use that instead and see how it goes?

(I *would* like to reduce the set of classes the new commands accept, to make it clearer which cases we need to have properly thought through, but links would certainly still be among those on the list, and in that regard perhaps delete is easier to deal with than chgrp anyway.)

[mtbcarroll]

Opened ​https://github.com/openmicroscopy/openmicroscopy/pull/3594 to get the idea out there more concretely.

Does deleteObject really need to deal with every possible OMERO model object, or just a healthy range, including ILinks and Shapes and whatnot?

One difference with using Delete2 is that, for instance, if deleting a shape upon which someone has commented, the deletion will now proceed and remove the comment too.

[mtbcarroll]

PR was merged.