[Geoserver-users] (no subject)

Bart,
you should put feature requests in the JIRA task tracker or they'll just
get lost.

1. http://jira.codehaus.org/browse/GEOS
2. hit "create new issue" (in the menu bar at the top)
3. (you might need to create an id)
4. make sure you set a "fix for" version (1.3.0 is a good one to attach
to).
5. you can create the issue in Geoserver or Geotools. Geoserver for
geoserver-related things, and Geotools for geotools related things.
Most low-level things should go in Geotools. Make sure you choose the
correct component.

--------------

3) are there plans to also update the Oracle datastore to pass Like
filters to the DB instead of evaluating them in Geotools?

They should just have to add a single line to the datastore and TEST. I
sent a message to the geotools list, but I dont know if they're going
to fix it. You'll have to ask there (you can also just submit a jira
task to the "oracle" section in geotools).

2) Distinct
Does Geoserver support or want to support the Distinct ogc function,
and would this perform runtime on semi-large databases (500.000

records)?

I dont think there is an OGC Distinct function. Whats the reference to
it?

1) case-insensitive search
How does Geoserver search, does it search case-sensitive or
case-insensitive when a non spatial filter is applied. Or does it
depend on the datastore? I am in need of case-insensitive search, for
Mapserver we started to use Filter 1.1 since this supports the

matchCase attribute.

There is no OGC case-insensitive search method. I dont think there's an
SQL-92 version either. Postgresql has a non-standard (?) ilike
function, but I dont think its in the offical SQL spec.

You can get the databases to handle this, but it'll take a little work:

1. create a functional index on the column you want to index.
   In postgresql it looks like this:

   CREATE INDEX my_lc_index ON <table> lower( <col name>)

   I'm not sure how to do it on oracle or other databases.

2. add functionality to the DB datastore to convert a filter like:

<PropertyIsLike>
   <PropertyName>mycol</PropertyName>
   <Function name="lower">
       <ogc:Literal>DAVEVILLE</ogc:Literal>
   </Function>
  </PropertyIsLike>

  to

   SELECT ... FROM ...
    WHERE mycol like lower('DAVEVILLE')

NOTE: this isnt "difficult", but non-trivial.
      I can help you do this if you want the functionality.

dave

----------------------------------------------------------
This mail sent through IMP: https://webmail.limegroup.com/

>3) are there plans to also update the Oracle datastore to pass Like
>filters to the DB instead of evaluating them in Geotools?

They should just have to add a single line to the datastore and TEST.
I
sent a message to the geotools list, but I dont know if they're going
to fix it. You'll have to ask there (you can also just submit a jira
task to the "oracle" section in geotools).

Bart, if you submit that to JIRA I'll attach the updated jar there.

Dave, theoretically the jdbc datastores shouldn't have to do anything.
Oracle (and others I believe) inherits it's filter capabilities from
the generic SQLEncoder, so if you added it there, then it should add it
in the children.

That said Oracle has some implementation of Like, which I'm going to go
ahead and assume doesn't work, and to just use your latest
implementation. Hopefully Bart can test out for us? Try it in Oracle
now and see what you get, and create a jira task and I'll get code that
uses Dave's.

Chris

----------------------------------------------------------
This mail sent through IMP: https://webmail.limegroup.com/