Recommended Envers data migration strategies?

dfisher95350 Jul 15, 2011 11:25 AM

Let's say I have two related application modules, each using its own SessionFactory, database schema and revision history schema. What should I consider if I want to merge them (and of course therefore their revision histories)? Or vice versa, if I have one I want to split to two? Or if I want to migrate only one entity from one to the other?

The main issue I see is this: won't I have to recollate (regenerate, reissue) my integer revision numbers (by date)?

1. Re: Recommended Envers data migration strategies?

adamw Jul 17, 2011 2:00 AM (in response to dfisher95350)

Merging could be tricky as you can have duplicated revision numbers, and after merging you could loose the bigger-revision-is-later invariant. Splitting on the other hand is easier, just pick the entities you are interested in

Adam
Actions