View Issue Details

IDProjectCategoryView StatusLast Update
000846510000-004: ServicesSpecpublic2022-12-06 15:32
ReporterMatthias Damm Assigned ToMatthias Damm  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Product Version1.05.00 
Target Version1.05.03 RC1Fixed in Version1.05.03 RC1 
Summary0008465: No definition for 'ordered value' in FilterOperator
Description

7.7.3 FilterOperator
Table 122 – Basic FilterOperator definition

The table has multiple places that have similar sentences 'Any operand that resolves to an ordered value.'

It is not defined what a ordered value is.

TagsNo tags attached.
Commit Version
Fix Due Date

Activities

Paul Hunkar

2022-11-28 05:37

developer   ~0018193

It is just the English sentence that means it resolves to a number or datetime or something that has a well known order to it (i.e. 10 > 20) or 10:00 1/1/2020 < 11:00 1/1/2020). It might be better to explain or define it better since some might think a string could also have a well known order to it (but maybe not all agree on what the order for strings would be)

Matthias Damm

2022-12-06 08:08

developer   ~0018233

7.7.3 FilterOperator

Added clarification:
Operands that resolve to an ordered value are restricted to the DataTypes Byte, Int16, Int32, Int64, SByte, UInt16, UInt32, UInt64, Float, Double and DateTime.

Jim Luth

2022-12-06 15:32

administrator   ~0018243

Agreed to changes in Virtual F2F.

Issue History

Date Modified Username Field Change
2022-11-27 16:00 Matthias Damm New Issue
2022-11-28 05:37 Paul Hunkar Note Added: 0018193
2022-11-29 17:29 Jim Luth Assigned To => Matthias Damm
2022-11-29 17:29 Jim Luth Status new => assigned
2022-12-06 08:08 Matthias Damm Status assigned => resolved
2022-12-06 08:08 Matthias Damm Resolution open => fixed
2022-12-06 08:08 Matthias Damm Fixed in Version => 1.05.03 RC1
2022-12-06 08:08 Matthias Damm Note Added: 0018233
2022-12-06 15:32 Jim Luth Status resolved => closed
2022-12-06 15:32 Jim Luth Note Added: 0018243