Envers revision cannot be found when the lookup is made based on an Instant
Description
Activity
Show:
Chris Cranford April 18, 2024 at 1:58 PM
Hi @Florian Heck yep I saw the PR after commenting, appreciate that. I added a comment about a test case on the PR, if you could follow-up on that, I’d be most appreciative.
Florian Heck April 18, 2024 at 1:56 PMEdited
@Chris Cranford We use a default setup but I’m pretty sure I already tract down the underlying bug and I have an PR ready with the fix. But the validation there mentioned that I need an issue number in my commit message so I’m in the process of linking them together.
Chris Cranford April 18, 2024 at 1:53 PM
Hi @Florian Heck , are you using the default revision entity or a custom revision entity in your set-up?
Fixed
Details
Details
Assignee
Florian Heck
Florian HeckReporter
Florian Heck
Florian HeckComponents
Affects versions
Priority
MajorCreated April 18, 2024 at 1:49 PM
Updated April 23, 2024 at 12:03 PM
Resolved April 19, 2024 at 10:35 AM
When retreving a revision for envers, in case the revision timestamp is persisted as a long (i.e. a unix timestamp with millisecond precision) and the request to resolve a revision is made with an object of type Instant, the resulting parameter is returned as a unix timestamp with seconds precision instead of the expected milliseconds. This leads to (usually) not finding any revisions.