I found the bug for the multitenency you described in 4.x:
https://hibernate.onjira.com/browse/HHH-6054. There is a comment on there
from Damien Hollis which describes one of the scenarios we face and have
solved with filters + persistence listeners. (I would like to note that
our solution is aut
Hi Hardy, not sure why but I received this email more than one hour
later after you've sent it.
Anyway, it's solved and it seems DB2 is working fine too:
https://hudson.qa.jboss.com/hudson/job/hibernate-search-master-dbmatrix-coreSnapshot/
Not sure what happened with oracle11gR1RAC, seems a git p
Hi,
I am trying to figure out why the Search DB2 test in Jenkins is still failing -
http://hudson.qa.jboss.com/hudson/job/hibernate-search-master-dbmatrix-coreSnapshot/database=db2-97,jdk=java16_default,label=hibernate/
When I run the test locally against Core 4.0.0-SNAPSHOT using the DB2 profi
I was upgrading Hibernate Search to depend on latest Hibernate Core
release, a very minor step but this broke the build.
In Search we're using
org.hibernate.PessimisticLockException.getEntity()
to convert it to a javax.persistence.PessimisticLockException when
using the JPA API.
It's not a hard
Ah good point, I haven't thought of that problem with query splitting
On 30 nov. 2011, at 22:20, Steve Ebersole wrote:
> Splitting is not always an option. Consider a predicate like:
>
> ... where a in (x1, ... x2000) and b in (y1, ... y2000) ...
>
> If you split this up, you will have misses.