Chris Holmes wrote: > They were made to be Filter.ALL and Filter.NONE. They're static > singleton constructs I think off the Filter main class. > > They should be really easy to implement, and I'd say you should just > implement them, you just have to do a query as if there was no filter, > and do a query to return nothing. Check the classes to see which is > which, I remember them being slightly weird.
I've refactored and added FilterType.NONE and FilterType.ALL. There is now only one instance of "12345" and "-12345". Please see JIRA GEOT-916 and GEOT-848. I haven't made any changes to what each SQLEncoder had defined as its Filter capabilities -- only *how* it is defined (in some cases there was a private filtercapabilities variable defined in the class, and the superclass method was obtaining a different variable -- so some differences may be present. Justin pointed out that Postgis does not support BEYOND, so this has been removed. ...now onto GEOT-917 (merge SQLEncoderPostgis and SQLEncoderPostgisGeos) Cheers, Cory. ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
