|
From: NHibernate J. <mik...@us...> - 2007-01-10 14:25:34
|
Filter parameter is mandatory and should be optional
----------------------------------------------------
Key: NH-857
URL: http://jira.nhibernate.org/browse/NH-857
Project: NHibernate
Type: Bug
Components: Core
Versions: 1.2.0.Beta2
Reporter: Luis Ferreira
Priority: Minor
When a filter is declared with no parameters, an exception is raised.
For instance, we'd like to have a filter such as:
<filter-def name="Autorizacoes" condition="Classe = 1">
So, results are accepted if a column has as value a specified constant (rather than something variable). The resulting exception is:
A first chance exception of type 'NHibernate.MappingException' occurred in BancoDePortugal.SI.REI.Negocio.DLL
Additional information: Denominacao.hbm.xml(39,5): XML validation error: The element 'filter-def' in namespace 'urn:nhibernate-mapping-2.2' has incomplete content. List of possible elements expected: 'urn:nhibernate-mapping-2.2:filter-param'.
Of course a possible workaround is using a parameter instead of the constant, and pass the constant every time... but it is odd.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.nhibernate.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
|