Hi Christian,
I think the main reason has been the lack of interest, and the additional
difficulties such an integration would bring in terms of proper
testing and maintenance.
There are some performance and efficiency tricks we can take
advantage of, but I don't remember of many on the top of my
Hi Emmanuel, All,
Thnx for taking time looking into this, my comments below.
On Tue, May 29, 2012 at 3:31 PM, Emmanuel Bernard
wrote:
> In a Document approach, there is no (useful) notion of association either but
> one can gather a set of elements under a property name. This is useful for
>
Hello!
I just looked into the Hibernate Search source code and was wondering
why you are using hibernates criteria API instead of JPA Criteria API? I
haven't looked deeper but actually this is the reason why it can't be
used with other JPA implementations, or are there any other dependencies
t
On Sun 27 May 2012 02:52:23 AM CDT, Łukasz Antoniak wrote:
> The initial question here is how to distinguish dialects that support
> statements like:
> update ParentEntity_AUD set REVEND=? where (id, REV) IN (select id,
> REV from HT_ChildEntity_AUD)
Ok. And this form comes about because of the m
That's an interesting problem that we started to scratch in the document
oriented approach.
In the key/value pair, the underlying system has no notion of association. The
table + column(s) mapping works great.
In a Document approach, there is no (useful) notion of association either but
one ca
