I have sets of tables that contain versioned data; one table acts as the parent
and the other contains the revisions of the parent. The parent record stores a
long PK and a string ID. The revisions table stores a long PK, the long PK of
the parent (with FK relationship), a replacement date (if n
Actually, I am reviewing the code to hack it, I append a sequence diagram of my
analysis, hotspotting in red the points where cayenne do some actions that
must be done post transaction commit but are actually done before transaction
commits. The sequence diagram shows the scenario where we are
