Title: Message Title
Jody Garnett created an issue
Hi,
I think I might have found a Class Cast bug where a StringBuilder is
expected but in certain cases a String is returned...It appears that
in org.geotools.filter.text.ecql.ECQL this method:
public static String toCQL( Filter filter ){
FilterToECQL toCQL = new FilterToECQL();
Thanks for the Reply! Is the access pattern or usage of the API in this
code incorrect then? It works for other filters but not for the id filter.
public class FilterFailTest {
@Test
public void test(){
FilterFactory ff =
CommonFactoryFinder.getFilterFactory(GeoTools.getDefaultHin
I think that is by design, the toCQL method is not a "visitor" but instead
a public utility method making it easier to call and use the visitor object.
I think we actually wrapped up all the utility methods into the CQL and
ECQL classes to make this stuff easier to use.
Jody
Jody Garnett
On Th
Hi,
I think I might have found a Class Cast bug where a StringBuilder is
expected but in certain cases a String is returned...It appears that in
org.geotools.filter.text.ecql.ECQL this method:
public static String toCQL( Filter filter ){
FilterToECQL toCQL = new FilterToECQL();
Title: Message Title
Andrea Aime created an issue
All your suggestions sound good, the locking manager is intended to be
pluggable, so you can implement locking in SQL if your database supports it.
Jody Garnett
On Thu, Apr 24, 2014 at 6:53 PM, Mauro Bartolomeoli <
mauro.bartolome...@geo-solutions.it> wrote:
> Hi,
> recently we hit a performan
Hi,
recently we hit a performance issue using the JDBCFeatureStore
removeFeatures method.
The problem is in the JDBCDataStore ensureAuthorization call that is
checking if all the features can be removed (no locks on them).
We launched a removeFeatures with a Filter.INCLUDE filter on a 1.000.000
r
