[daisy] [JIRA] Resolved: (DSY-403) More lenient valuetype comparison
Bruno Dumon (JIRA)
issues at cocoondev.org
Thu Apr 26 07:13:20 CDT 2007
[ http://issues.cocoondev.org//browse/DSY-403?page=all ]
Bruno Dumon resolved DSY-403:
-----------------------------
Fix Version: 2.1
Resolution: Fixed
Applied as part of SVN rev 3991.
> More lenient valuetype comparison
> ---------------------------------
>
> Key: DSY-403
> URL: http://issues.cocoondev.org//browse/DSY-403
> Project: Daisy
> Type: Improvement
> Components: Querying and indexing (repository)
> Versions: 2.0
> Reporter: Paul Focke
> Priority: Minor
> Fix For: 2.1
> Attachments: valuetypecompatibility.patch
>
> At the moment in order to compare values they must be of the exact same valuetype. This occurs in all kinds of comparing query functions like 'between', '>', '<', '=', ...
> If a measure could be introduced to specify which datatypes are compatible with eachother then comparison functions might be more versatile in their usage.
> Whenever math functions are used in a comparison then errors occur at the moment. Like in the clause '$LongField1 > ContextDoc($LongField2 + 5) ' then $LongField1 will be of type long while 'ContextDoc($LongField2 + 5) ' will be of the type decimal.
> If it were set somewhere that decimals were compatible with longs and longs compatible with decimals then checking on compatiblity instead of equal valuetypes ought to make the above statement work.
> In the QValueType enum there is already a method available for checking on compatiblity but it is rarely used and quite limited. So expanding this method and using it more might be a possible solution.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.cocoondev.org//secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
More information about the daisy
mailing list