View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0008465 | 10000-004: Services | Spec | public | 2022-11-27 16:00 | 2022-12-06 15:32 |
Reporter | Matthias Damm | Assigned To | Matthias Damm | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Product Version | 1.05.00 | ||||
Target Version | 1.05.03 RC1 | Fixed in Version | 1.05.03 RC1 | ||
Summary | 0008465: No definition for 'ordered value' in FilterOperator | ||||
Description | 7.7.3 FilterOperator 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. | ||||
Tags | No tags attached. | ||||
Commit Version | |||||
Fix Due Date | |||||
|
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) |
|
7.7.3 FilterOperator Added clarification: |
|
Agreed to changes in Virtual F2F. |
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 |