To be more clear... A filter is there to be used as filter of entities/collections and not to filter what should be a SimpleValue property (a string for example). There are users using a filter to be applied to a SimpleValue property with a formula and may cause ugly issues in some complex queries (with join fetch etc.).
2010/1/13 Fabio Maulo <[email protected]> > No Oren, I'm talking about others 4 or 5 issues appeared since NH2.0 and > all related with the wrong, and obviously not documented, usage of filters. > In the documentation a filter is to filters classes and/or collections and > each filter must have a condition. > We have talked about this matter in dev-list too. > > btw, if you want remove the exception, please, leave the log.Error (in the > future we must know why an issue is there). > > > 2010/1/13 Ayende Rahien <[email protected]> > >> Not sure that I am following, I just run the full test scenario and wasn't >> able to figure it out. >> Are you talking about :FilterName.ParameterName hack? >> >> >> On Wed, Jan 13, 2010 at 5:34 PM, Fabio Maulo <[email protected]>wrote: >> >>> parameters stuff... there was others 4 or 5 issues caused by the wrong >>> usage of filters. >>> >>> 2010/1/13 Ayende Rahien <[email protected]> >>> >>> I am looking at this: http://nhjira.koah.net/browse/NH-2064 >>>> >>>> Defining filters without using them in classes. >>>> There is a comment there that I am not sure that I understand: >>>> >>>> // if you are going to remove this exception at least add a log.Error >>>> // because the usage of filter-def, outside its scope, may cause >>>> unexpected behaviour >>>> // during queries. >>>> >>>> What unexpected behavior might be from unused filter definition? >>>> >>> >>> >>> >>> -- >>> Fabio Maulo >>> >>> >> > > > -- > Fabio Maulo > > -- Fabio Maulo
