Hibernate version: 3.0.5

Alright, somewhat of an odd situation here.

Let's say I've got a table, INFO. INFO has a "child" table, INFO_LOCK, which acts like a one-to-one (the PK for INFO is the PK for INFO_LOCK).

We can fake it as a one-to-one relationship in Hibernate, and this works well.

The INFO table gets too large and is then split into INFO and INFO_ARCHIVE

INFO and INFO_ARCHIVE are exactly the same structure; they just have different sets of data.

Both tables still have the same "one-to-one" association to INFO_LOCK.

How would you best represent this in Hibernate?