On Thursday 27 May 2010 10:58:48 am Mauricio Pazos wrote: > On Thursday 27 May 2010 10:48:13 am Mauricio Pazos wrote: > > > Possible ways out: > > > - use an identifier that's very unlikely or downright wrong as an > > > attribute name. Something like @id or ::id or id() (just making them > > > up, did not check if I'm actually introducing other problems with > > > any of them). > > > - turn that into a pseudo function call, something like > > > id_in(id1, id2, ..., idn) A sentence like this works and it has not conflicts with other sentence. I must to check the ECQL grammar details. Following this idea the options could be id_in(id1, id2, ..., idn) or id(id1, id2, ..., idn) or in(id1, id2, ..., idn) more?
> > > - have escapes to state ID is intended to be used as an attribute. > > > "ID" would work I guess > > > > I like this option, it matches with SQL convention (cql is sql like), and > > we could apply the same criteria for all keyword. > > > > LIKE is Keyword, "LIKE" is attribute > > BEFORE is keyword, "BEFORE" is attribute We could use this strategy to scape keyword. in this scenario the ID not need to be a keyword in the ECQL grammar. -- Mauricio Pazos www.axios.es ------------------------------------------------------------------------------ _______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
