Revision.revision_date comes from the system timestamp where the revision was committed. With clock problems and merging revisions from other branches, the revision_date is not always in order. To retrieve a set of revisions that landed on a branch during a particular timeframe, we need to remember the min and max of BranchRevision.sequence during that timeframe. Or store BranchRevision.date_created as the time the branch scanner loaded the BranchRevision record into the database.
I suspect the query is broken.
Revision. revision_ date comes from the system timestamp where the revision was committed. With clock problems and merging revisions from other branches, the revision_date is not always in order. To retrieve a set of revisions that landed on a branch during a particular timeframe, we need to remember the min and max of BranchRevision. sequence during that timeframe. Or store BranchRevision. date_created as the time the branch scanner loaded the BranchRevision record into the database.