My three questions are
1. Is it reasonable to expect that ECQL.toCQL/toFilter should be inverses?
>
If it is reasonable if you supply a patch :) I figured it was reasonable
and patched a couple of gaps here:
https://jira.codehaus.org/browse/GEOT-4783
In particular you can review the patch
https://github.com/geotools/geotools/commit/649853a304a4779ed86121151193ea0fe049f367
to see how I handled recognising part of a filter as being representable as
ECQL, and then creating a method to output the ECQL.
if (isInFilter(filter)) {
return buildIN(filter, extraData);
}
// default to normal OR output
return FilterToTextUtil.buildBinaryLogicalOperator("OR", this,
filter, extraData);
> 2. If my issue is a bug, can I submit a PR, etc? Is there documentation
> about that process?
>
Yep, there is a CONTRIBUTING.md
<https://github.com/geotools/geotools/blob/master/CONTRIBUTING.md>file
(which is shown as a link when you issue a github pull request). Or see
the home page about getting involved <http://geotools.org/getinvolved.html>.
3. Has anyone else run into this? Is there a well-known work-around?
>
I don't think many people rely on ECQL.toCQL/toFilter being invertible. So
lets just get it done.
--
Jody
------------------------------------------------------------------------------
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls.
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
_______________________________________________
GeoTools-Devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
