Re: [hibernate-dev] [OGM-452] Abstraction work between OGM internal keys and Infinispan cache keys

[Gunnar Morling]

Hi,

I've sent PR https://github.com/hibernate/hibernate-ogm/pull/408 for this.
It's done, only docs are missing. The strategy to be used (CACHE_PER_KIND
vs. CACHE_PER_TABLE) is configurable via a property, CACHE_PER_TABLE being
the default.

Any feedback welcome.

--Gunnar


2014-11-14 17:39 GMT+01:00 Emmanuel Bernard :

> Hi Gunnar,
>
> I have not implemented the new strategy yet but here is the first pass on
> the abstraction and contract to allow the ogm key / cache key split.
> Take a look if you have time.
>
> https://github.com/emmanuelbernard/hibernate-ogm/tree/OGM-452
>
> I need to implement the new cache key types, their marshallers and eagerly
> initialize all caches.
> ___
> hibernate-dev mailing list
> hibernate-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev

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

[Oskar Berggren]

Hi,

The Hibernate documentation (section 10.1.5. Table per concrete class
http://docs.jboss.org/hibernate/orm/4.3/manual/en-US/html/ch10.html#inheritance-tableperconcrete
) says:

> If your superclass is abstract, map it with abstract="true". If it is not
abstract,
> an additional table (it defaults to PAYMENT in the example above), is
needed
> to hold instances of the superclass.

Why is this keyword needed? Couldn't abstract classes be detected
automatically using reflection?


/Oskar
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev