-
Notifications
You must be signed in to change notification settings - Fork 100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RevisionMetadata cannot handle RevisionTimestamp in TIMESTAMP format #135
Comments
If you map it to a |
Oh, wait. Now I get you. I guess the relevant parts are missing in Spring Data Commons' |
I've filed |
That's fixed for Lovelace and Kay. Would you mind trying the latest snapshots? |
Definitely! Thanks for the quick reaction. I was just about forking the repo when you confirmed it's already done. I will come back at you, as soon as I tried it. |
@olivergierke we have tried the latest snapshots and it works fine. Thank you for the quick reaction! |
Awesome, thanks for confirming. |
Is there documetation that explains how to achieve the transformation? |
Well I figure it out and it might worth to add it to some documentation. This is what I did for Derby: My class looks like:
and my ddl looks like:
|
Hi folks,
I started using Hibernate Envers natively and created my own RevisonInfo and REVINFO table. I used TIMESTAMP as data type for the RevisionTimestamp and mapped it to java.util.Date, which is fine for Hibernate.
Now we are starting to use spring-data-envers and run into the following issue:
RevisionMetadata expects the RevisionTimestamp to be either an Instant, LocalDateTime Long, while Hibernate supports only Long, java.util.Date or java.sql.Date.
I could switch to long, but I would prefer to keep a readable format in the database.
Is there any way out of this? I wonder why spring-data-envers, which wraps Hibernate Envers, is supporting different types.
Cheers,
Stefan
The text was updated successfully, but these errors were encountered: