On Tuesday, February 7, 2017 at 12:13:15 PM UTC+1, Oskar Berggren wrote: > > I've done it on a higher level, and based on linq. Instead of starting > with session.Query<T>() I start with session.QueryAccessible<T> when I > write queries. Collection properties are not filtered when loaded by > association in my scenario. >
I do this as well right now, but I don't find it good enough exactly because you cannot filter collections when loaded by associations. This may cause serious security bugs. It seems like we are lacking an event of some kind where we can attach the logic. The OnPrepareStatement receives a SqlString which is, as far as I understand, pretty difficult to manipulate in a sane way. Unless you have to attach the same piece of query regardless the object being queried. -- You received this message because you are subscribed to the Google Groups "nhusers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/nhusers. For more options, visit https://groups.google.com/d/optout.
