Bug #1470
TBX: 0.7.7, CQP attribute names cannot use CQL operator names
Status: | New | Start date: | 09/03/2015 | |
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | - | % Done: | 0% |
|
Category: | SearchEngine | Spent time: | - | |
Target version: | TXM X.X |
Description
A corpus using the name 'cat' for a word property (positionnal attribute) breaks CQP: it is impossible to query that property in any CQL expression.
The problem has only been reported for the 'cat' operator name, but all CQL operator names are probably affected: asc, ascending, by, cat, cd, collocate, contains, cut, def, define, delete, desc, descending, diff, difference, discard, dump, exclusive, exit, expand, farthest, foreach, group, host, inclusive, info, inter, intersect, intersection, join, keyword, left, leftmost, macro, maximal, match, matchend, matches, meet, MU, nearest, no, not, NULL, off, on, randomize, reduce, RE, reverse, right, rightmost, save, set, show, size, sleep, sort, source, subset, TAB, tabulate, target, target[0-9], to, undump, union, unlock, user, where, with, within, without, yes
Solution 1¶
- a) in all import processes produce an error message and abort for any word property that is the same name as a CQL operator.
- b) document the fact that no CQL operator name should be used as a word property name in sources.
Solution 2¶
Develop in CQP the possibility to use CQL operator names for word property names (positionnal attribute name).
History
#1 Updated by Serge Heiden almost 8 years ago
- Description updated (diff)
#2 Updated by Matthieu Decorde over 7 years ago
- Target version changed from TXM 0.7.8 to TXM 0.8.0a (split/restructuration)
#3 Updated by Sebastien Jacquot almost 5 years ago
- Target version changed from TXM 0.8.0a (split/restructuration) to TXM 0.8.0
#4 Updated by Matthieu Decorde about 4 years ago
- Target version changed from TXM 0.8.0 to TXM X.X