Comment 4 for bug 1424593

Apparently that is caused by .one() method populating object into the active session.
When calling query.delete() this object is deleted from the session, and already is absent in the db which leads the the trace above.

Need to avoid synchronizing session on delete.