gvSIG bugs #2854
The NOT operator doesn't always work in Filter expressions
Status: | Outdated | % Done: | 0% | |
---|---|---|---|---|
Priority: | Normal | Spent time: | - | |
Assignee: | - | |||
Category: | Document table | |||
Target version: | - | |||
Severity: | Minor | Add-on version: | ||
gvSIG version: | 2.1.0 | Add-on build: | ||
gvSIG build: | 2247 | Add-on resolve version: | ||
Operative System: | Add-on resolve build: | |||
Keywords: | expression, filter, not | Proyecto: | ||
Has patch: | Hito: | |||
Add-on name: | Unknown |
Description
The NOT operator doesn't always work in Filter expressions.
In detail, NOT <condition> is considered as an invalid expression, while NOT (<condition>) is not applied at all.
Furthermore, the expressions containing NOT LIKE work, while with NOT IN or NOT EXISTS not.
History
#1 Updated by Álvaro Anguix over 9 years ago
- Category set to Document table
#2 Updated by Álvaro Anguix over 5 years ago
- Status changed from New to Outdated
With the new Filter tool this bug won't be fixed