Menu

#43 - in attribute names breaks the search

open
nobody
5
2004-11-24
2004-11-04
myrosia
No

The following query produces an error

($a segment) : ($a@start-type == "PVE")
Lexical error at line 1, column 26: encountered "t"
(116) after "-".

I tried the obvious choices (quoting the attribute
name, backslashing the -) with no result.

I can obviously do a search and replace on my data, to
get rid of "-" in attribute names, but it would be
better to have it supported, given that this is valid xml.

Myrosia

Discussion

  • J Carletta

    J Carletta - 2004-11-11

    Logged In: YES
    user_id=858324

    Namespacing breaks the query engine as well (e.g.,
    the attribute nite:id). For this reason we usually
    avoid namespacing even the reserved attributes in
    a corpus, although it would be better to support
    namespacing.

    Jean

     
  • J Carletta

    J Carletta - 2004-11-11

    Logged In: YES
    user_id=858324

    Namespacing breaks the query engine as well (e.g.,
    the attribute nite:id). For this reason we usually
    avoid namespacing even the reserved attributes in
    a corpus, although it would be better to support
    namespacing.

    Jean

     
  • J Carletta

    J Carletta - 2004-11-11

    Logged In: YES
    user_id=858324

    Namespacing breaks the query engine as well (e.g.,
    the attribute nite:id). For this reason we usually
    avoid namespacing even the reserved attributes in
    a corpus, although it would be better to support
    namespacing.

    Jean

     
  • J Carletta

    J Carletta - 2004-11-24
    • labels: 624962 --> query language