On Mon, Mar 5, 2012 at 9:51 PM, Steve Ebersole wrote:
> Hm, then I do not actually understand the first query either. Are these
> query results cached?
Nope, no cache yet.
I'm going to work on a simple Maven project so that you can reproduce
the problem easily.
Have a nice day.
--
Guillaume
Hm, then I do not actually understand the first query either. Are
these query results cached?
On Wed 29 Feb 2012 03:16:48 PM CST, Guillaume Smet wrote:
> On Wed, Feb 29, 2012 at 7:50 PM, Steve Ebersole wrote:
>> How are you loading these? Using Query#iterate I assume?
>
> We are using:
> entit
On Wed, Feb 29, 2012 at 7:50 PM, Steve Ebersole wrote:
> How are you loading these? Using Query#iterate I assume?
We are using:
entityManager().createQuery(query).getResultList(); and AFAICS in the
stacktrace Query#list.
___
hibernate-dev mailing list
How are you loading these? Using Query#iterate I assume?
On Wed 29 Feb 2012 11:21:36 AM CST, Guillaume Smet wrote:
> Hi,
>
> It's not something new as we checked that it was already the case with
> Hibernate 3.6 but we just hit an annoying problem with @OneToOne
> annotation if the relation is bi
Hi,
It's not something new as we checked that it was already the case with
Hibernate 3.6 but we just hit an annoying problem with @OneToOne
annotation if the relation is bidirectional.
Simplified example:
class A {
@OneToOne(cascade = CascadeType.ALL, orphanRemoval = true)
private
