In my application, I have defined a global filter on Tenant Id. I do this to enforce tenant security, so that developers do not accidentally create queries that allow information to cross tenant boundaries.
The problem I am having is that when I create queries that eagerly fetch associations, the queries produce sql that uses left outer joins, and the tenant filter is being applied to the entities in the left outer join in the where clause. This essentially acts like an inner join, and I end up losing records. Has anyone experienced this same problem with NHibernate filters. Is there a way to work around this so that I can still enforce this type of security and still keep my outer joins in tact? Just to clarify, this is an example of a filter: http://ayende.com/blog/3993/nhibernate-filters Your help is greatly appreciated. -- You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
