This content has been marked as final.
Show 3 replies
-
1. Re: Hibernate Envers with partitioned database
adamw Apr 23, 2013 10:06 AM (in response to timdua)Well, the audit entity's id is composed of the revision number + primary key for the audited entity. So if the entity contains the company id in its primary key, it should work.
Adam
-
2. Re: Hibernate Envers with partitioned database
timdua Apr 23, 2013 10:52 AM (in response to adamw)Thanks for answering my question but the way we would like it to function is the following:
The revision number should increase per company like that:
companyId revision number
10000008 1
10000008 2
10000009 1
10000009 2
10000009 3
That way we could easily copy company data (also the company audit data itself) from one server to another without having conflicting keys.
-
3. Re: Hibernate Envers with partitioned database
adamw Apr 24, 2013 10:43 AM (in response to timdua)Maybe this would be possible with a custom revision entity and a custom id generation strategy?
Adam