Comments on: Howto Keep Version History in a Single Table Using Hibernate http://www.rojotek.com/blog/2007/12/07/howto-keep-version-history-in-a-single-table-using-hibernate/ Software Development in Brisbane Fri, 03 Feb 2012 20:00:10 +0000 hourly 1 http://wordpress.org/?v=3.1.3 By: Ido Ran http://www.rojotek.com/blog/2007/12/07/howto-keep-version-history-in-a-single-table-using-hibernate/comment-page-1/#comment-21675 Ido Ran Fri, 20 Feb 2009 15:10:15 +0000 http://www.rojotek.com/blog/2007/12/07/howto-keep-version-history-in-a-single-table-using-hibernate/#comment-21675 Hi, I'm looking for the solution of the problem you just describe - save history in the same table. I've also got to the solution you suggest here. The problem start when you have referenced table, in that case you end up with either of two options (both of them are not good for the solution): Have two ID columns, one called IID (for Internal ID) which will be the primary key of the table and another one called GID (for Global ID) which will be the same for all records represent the same entity. The other option is to have a complex primary key build of both the ID (GID in a since) and the version. No matter which one you pick you end up referencing the first table to a specific version of the entity, not the entity itself. It means that when every you update the referenced entity you will have to go over all the referencing entities and update them so they'll reflect the updated data. I'll be glad to know if you find a good solution for that. Thank you very much, Ido. Hi,
I’m looking for the solution of the problem you just describe – save history in the same table.
I’ve also got to the solution you suggest here.
The problem start when you have referenced table, in that case you end up with either of two options (both of them are not good for the solution):
Have two ID columns, one called IID (for Internal ID) which will be the primary key of the table and another one called GID (for Global ID) which will be the same for all records represent the same entity.
The other option is to have a complex primary key build of both the ID (GID in a since) and the version.

No matter which one you pick you end up referencing the first table to a specific version of the entity, not the entity itself. It means that when every you update the referenced entity you will have to go over all the referencing entities and update them so they’ll reflect the updated data.

I’ll be glad to know if you find a good solution for that.

Thank you very much,
Ido.

]]>