Re: [hibernate-dev] Why must abstract be specified in mappings?

This is a user related question that should go on our forums https://forums.hibernate.org But to answer you, you sometimes want to have a physical table for that abstract class. So Hibernate ORM’s “abstract” really means map it to a table or not. Java’s abstract

Re: [hibernate-dev] Why must abstract be specified in mappings?

2014-11-25 9:29 GMT+01:00 Emmanuel Bernard : > This is a user related question that should go on our forums > https://forums.hibernate.org > It's intended as a question/discussion on the design of Hibernate, which is why I thought it was relevant here. The background is that the same question has

[hibernate-dev] [OGM] storing the column names in the entity keys for K/V stores

Hi, With OGM-452 behind us which brings one cache per “table”, we now have another decision in front of us. Should we use a synthetic key for the cache key (say a PersistentEntityKey class containing the array of column names and the array of column values)? Or should we use the natural object ke

Re: [hibernate-dev] Why must abstract be specified in mappings?

There is also the case of non-POJO entities... But the issue is a matter of timing. At the time this information is used (to create the "denormalized table" mapping) we do not yet know the entity Class reference. So it is a matter of practicality given the current Configuration/mapping design.

Re: [hibernate-dev] Why must abstract be specified in mappings?

Ah you mean for tooling that might not have access to the classpath (assuming the class based entity mode)? Regardless of this Oskar, you are correct, it seems I got it backwards. It would be to express that a non abstract class has no instance and thus no table should be created. If you are wor