d filters work as intended. Can you explain a little about
> why it was intended to ignore the active filters when doing a find?
> And why respecting the filters on a find is bad?
>
> Thanks,
>
> Jason Clawson
>
>
>
> Sent from my iPhone
>
> On Nov 30, 2011, at
respecting the filters on a find is bad?
Thanks,
Jason Clawson
Sent from my iPhone
On Nov 30, 2011, at 7:30 AM, Steve Ebersole wrote:
> What you are doing is called multi-tenancy.
>
> Hibernate 4 has more explicit support for multi-tenant data. Unfortunately
> 4.0 only support
imple equality check in java. The best, most
performant, solution is to be able to apply the filter clause to the
EntityManager.find operation.
What is your take on this?
Thanks,
Jason Clawson
___
hibernate-dev mailing list
hibernate-dev@lists.jboss
I am curious as to why the decision was made to not append a WHERE clause to
deletes and updates that could be affected by a session filter. I was
looking at the source for HqlSqlWalker.postProcessDML, and it has the
comment "append any filter fragments; the EMPTY_MAP is used under the
assumption