On Jun 25, 2012, at 2:48 PM, Marc Schipperheyn wrote:
> The TwoWayFieldBridge issue seems similar to what I'm suggesting and would
> seem to resolve most of my issues.
Then I think we should focus on this. I need to refresh my memory on where we
stand in the discussion around this issue.
--H
The TwoWayFieldBridge issue seems similar to what I'm suggesting and would
seem to resolve most of my issues.
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
Hi Marc,
you bring up an interesting topic. For me this is related to a whole bunch of
outstanding
issues, especially when it comes to a way to optimize how ClassBridges work.
The issues I am referring to are :
* https://hibernate.onjira.com/browse/HSEARCH-764
* https://hibernate.onjira.com/br
@Transient @Field and @ClassBridges mark methods and classes dirty by
default because there is currently no way for HSearch to know which fields
are managed here. In the case of @Transient @Field this will often be ok,
because it will only lead to some superfluous extra indexing which is not a
big
