How do you guys feel about making a language that is a bit more lax? Now that we have the starting point?
I am thinking specifically of making one that has: a) support for filters that match what geotools can do: CQL: propertName contains geometry TXT: geometry contains propertyName b) some kind of fid filter CQL: n/q TXT: #road.1 Did you guys ever review my port of Eclesia's CQL encoder? It is committed with test cases... it generates the TXT format mentioned above (so it is not always valid CQL) Jody > On Tuesday 08 January 2008 06:35:23 pm Jody Garnett wrote: > >> So If I understand the comments we need to change the expression to use >> single quotes? The problem is just that the expression was invalid? >> > Indeed, though it was supported on a previous version of the CQL module, its > true the language defines a string literal to be bound to single quotes, so > it'd be better to stick to what the language says. > > >> Mauricio Pazos wrote: >> >>> Today I analyze the bug, please see the comments in >>> >>> http://jira.codehaus.org/browse/GEOT-1655 >>> >>> I am copying this mail to Andrea perhaps he have interesting comments. >>> >>> cheers >>> >> !DSPAM:4045,4783b461194471628642973! >> > > > ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
