Presently, we are migrating from hibernate 2 to hibernate 4 , we are facing issues for duplicate keys.

In Hibernate 2 we have multiple rows with same composite key combination but still data is coming as its expected.

In Hibernate 4 we not getting results as expected , Its coming duplicate as multiple rows exists with same composite key combination.

I was wondering why Hibernate 2 not considering duplicate ids to refer the objects, and is there some configuration available in hibernate 4 which will help avoid duplication of data if rows have same IDs

The issue is too vague to provide the right answer. Check out this article for more details on how you should implement a Composite Key with JPA and Hibernate.

Now, you said that:



This cannot be true because the DB will not allow two rows with the same Primary Key. It's the C in ACID that prevents this from happening. Maybe you were not using a Composite Key in Hibernate 2, but a synthetic one, like an IDENTITY or a SEQUENCE-based one.

Hi Vlad
Thanks For the quick reply ,
I agree with u that "This cannot be true because the DB will not allow two rows with the same Primary Key" , so the problem is that there is a existing database which can't be changed and there are no composite key and primary key constraints on Views.
In all preexisted hbm files, columns which are defined as id and composite id are not actually primary key and composite key in views.
In old set up with hibernate 2 the values are coming different for rows having same value for ID fields , but in my new set up with same hbm files first row is repeated for all records returned as all rows have same ID.


hence Wanted to know if there is any configuration that is done in hibernate 2 for this to happen ,which I missing. Secondly is that possible in hibernate 4

regards

I'm not aware of any such setting. But then, it's not very clear what the problem is. I understand that you can't change the DB schema, but the read-only View still needs a unique identifier or a combination of columns so that you can reference each individual row. I'm not sure how Hibernate 2 worked, I've never actually used this very old version. But if you want to upgrade, you have to provide such a unique identifier.

This would be a workable solution for my case : https://forum.hibernate.org/viewtopic.php?f=1&t=941182