A quick update on some more exploration on this:
it turns out sorting on a NumericField when this field is also using
an "indexNullAs" token gets the UninvertingReader approach to throw an
exception.
My two conclusions:
- we need to move away from supporting those tokens in NumericField,
especiall
On Fri, Aug 7, 2015 at 1:14 PM, Sanne Grinovero wrote:
> A quick update on some more exploration on this:
> it turns out sorting on a NumericField when this field is also using
> an "indexNullAs" token gets the UninvertingReader approach to throw an
> exception.
> My two conclusions:
> - we need
I thought we had discussed this once upon a time, but I could not find any
email. In overhauling the documentation I ran across our long-standing
recommendation that all associations be defined in metadata as lazy. JPA
of course came along said that for to-one associations the default should
eage
https://github.com/wildfly/wildfly/pull/7909 uses the Narayana
org.jboss.tm.listener.TransactionListenerRegistry to be notified when
the transaction is associated/deassociated with the JTA transaction.
I think that Hibernate ORM could do something similar with the
org.jboss.tm.listener.Transact
On 08/07/2015 11:41 AM, Steve Ebersole wrote:
> I thought we had discussed this once upon a time, but I could not find any
> email. In overhauling the documentation I ran across our long-standing
> recommendation that all associations be defined in metadata as lazy. JPA
> of course came along sa
Yeah, which is great when you can rely on impl-specific apis.
I'll consider this, but its not super high on my priority list. I guess we
could implement some kind of way for the JtaPlatform to indicate the "type
of timeout tracking" to do and develop a new NarayanaJtaPltaform that does
this.
On
For details, see
http://in.relation.to/2015/08/07/hibernate-orm-4220-final-and-4311-final-released
.
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
In working through the document overhaul I ran across the following passage
in the JPA specification:
The persistent state of an entity is represented by instance variables,
which may correspond to JavaBeans properties. An instance variable must be
directly accessed only from within the methods o
