On 29 January 2015 at 16:25, Gunnar Morling wrote:
> 2015-01-29 9:42 GMT+01:00 Hardy Ferentschik :
>>
>> Hi,
>>
>> > It would be nice to simply remove the references to @Key in the
>> > documentation, and avoid trying to explain when to choose between the
>> > two alternatives.
>> >
>> > This woul
Hi,
I would like to summarize a discussion we had on IRC to get some more feedback
and come to
a decision on how to move forward.
I am currently in the need of extending our serialization support for the
distributed Search
deployment scenarios. Basically we are serializing our different Lucen
Hi,
for a couple days my master build of Search is broken. The integration test
SearchNewEntityJmsMasterSlaveUsingInfinispanAs2ndCacheAndModulesIT
fails:
Failed tests:
SearchNewEntityJmsMasterSlaveUsingInfinispanAs2ndCacheAndModulesIT>SearchNewEntityJmsMasterSlave.searchNewMembersAfterSynchroniz
We have an EAP 6/Hibernate 4 customer looking for an enhancement for
envers for which there is an existing "Closed - Won't Fix" Jira:
https://hibernate.atlassian.net/browse/HHH-3555
Before I create an RFE, wanted to make sure there was no obvious reason
I shouldn't begin the enhancement request p
So here is what I have for implicit naming strategy, in simplified form:
1. Table naming
1. Entity primary table - @Table
2. Join table - @JoinTable
3. Collection table - @CollectionTable
4.
2. Column naming
1. basic attribute column
2. entity discrimina
