Historically natural-id look ups were accomplished by leveraging
Criteria queries. Caching was handled through the second level query
cache.
One of the new things in 4.1 is the dedicated natural-id loading API.
So the caching will be quite different here. I am a little leery about
making a b
nm, clean and then test worked
On 01/20/2012 11:30 AM, Steve Ebersole wrote:
> Everyone else seeing these after pulling master?
>
>
> Test
> org.hibernate.test.cascade.circle.MultiPathCircleCascadeCheckNullibilityFalseTest
> FAILED
> Test org.hibernate.test.cascade.circle.MultiPathCircleCascadeTes
we got a hibernate4 compatible fork in hibernate tools eclipse plugin now.
anyone want to contribute
and help make the now three releases that is needed? (3.2-3.5, 3.6 and 4.0?)
output of hibernate tools work with all versions, its only if you do queries or
need something specific
from hibernate
Everyone else seeing these after pulling master?
Test
org.hibernate.test.cascade.circle.MultiPathCircleCascadeCheckNullibilityFalseTest
FAILED
Test org.hibernate.test.cascade.circle.MultiPathCircleCascadeTest FAILED
Test
org.hibernate.test.cascade.circle.MultiPathCircleCascadeCheckNullTrueDel
Hi Mr. Andersen,
>>Problem is that it seems 4.1 will cause similar disjunct API
The "Redesigned metamodel" goal, which was planned for 4.1, surely would have
caused lots of disjunct API's again,
but now I saw on the hibernate roadmap, that in meantime the "Redesigned
metamodel" goal has been
