User can query for which objects have been deleted.

[jamoore]

Problem

Any use of org.hibernate.Query.executeUpdate will NOT cause an EventLog to be created, and therefore may should be avoided.

$ find omero.git/ -name "*.java" -exec grep executeUpdate {} /dev/null \;
omero.git//components/blitz/src/ome/services/blitz/fire/Ring.java:                this, "executeUpdate - set closed = now()") {
omero.git//components/blitz/src/ome/services/blitz/fire/Ring.java:                return q.executeUpdate();
omero.git//components/blitz/src/ome/services/blitz/fire/Ring.java:                return q.executeUpdate();
omero.git//components/server/src/ome/services/delete/DeleteBean.java:                    count = q.executeUpdate();
omero.git//components/server/src/ome/services/delete/DeleteBean.java:                    count = q.executeUpdate();
omero.git//components/server/src/ome/services/delete/DeleteBean.java:                count = q.executeUpdate();
omero.git//components/server/src/ome/services/delete/DeleteBean.java:                count = q.executeUpdate();
omero.git//components/server/src/ome/services/delete/DeleteBean.java:                count = q.executeUpdate();
omero.git//components/server/src/ome/services/delete/DeleteBean.java:                q.executeUpdate();
omero.git//components/server/src/ome/services/sessions/SessionManagerImpl.java:                    // Not performed! Session s = executeUpdate(sf, oldsession,
omero.git//components/server/src/ome/services/sessions/SessionManagerImpl.java:                    Session s = executeUpdate(sf, oldsession, userId);
omero.git//components/server/src/ome/services/sessions/SessionManagerImpl.java:                return executeUpdate(sf, copy, newctx.getCurrentUserId());
omero.git//components/server/src/ome/services/sessions/SessionManagerImpl.java:    private Session executeUpdate(ServiceFactory sf, Session session,
omero.git//components/tools/OmeroImporter/src/ome/formats/importer/HistoryDB.java:        int i = st.executeUpdate(expression);    // run the query

Solution

The solution requiring the least server modifications is to move all creation of delete EventLogs into the database as triggers.

Something similar was added for catching annotation modifications in #1390.

[jmoore]

Can't be fixed for 4.1. Carlos, what will you need in the way of a workaround?

[jmoore]

The same goes for any thing modified from psql. Note: such changes will ultimately cause lucene (and possibly other processes) to get out of sync. The best solution may be to add triggers at the DB level, so that any modifications will automatically create an EventLog? (this assumes an Event being present which complicates matters.)

[jmoore]

Changing to story to be a part of the delete refactoring requirement (#2615) This most likely entails adding triggers for all changes.

[jmoore]

Any other work on the reporting will have to be done as part of #2911. Closing.