I think I need to break something :(
Very early on in the project, when Hibernate queries just returned a
single-column result sets containing entities, I made a decision to have
Hibernate always return distinct result sets. It sort of made sense at the
time but now that Hibernate queries can ret
we r also using hibernate in a production environment. this change makes
sense and is not a big deal for us, so go for it.
brad
- Original Message -
From: "Jon Lipsky" <[EMAIL PROTECTED]>
To: "Christian Bauer" <[EMAIL PROTECTED]>;
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, August 07, 2002
On 07 Aug (11:11), Gavin_King/[EMAIL PROTECTED] wrote:
> What I would really like to do is push responsibility for this into the
> application by allowing the DISTINCT keyword in the Hiberante query and
> remove the select="distinct|all" mapping attribute.
>
> Unfortunately, this change would bre
> Anyone have any ideas why this is happening and/or how to fix it?
Its possibly a problem with the commons-logging stuff (i've seen some funny
things happen before with serialization). Could you try commenting out all
the references to commons logging in cirrus.hibernate.impl.LazyInitializer?
If
