Jody Garnett wrote:
Hi Marc you are the oracle module maintainer, I am also CCing the
geoserver and udig lists to give them an update.
I have been chatting with you on and off the last while, but I need to
do something public by way of getting our house in order.
I have created a a page for the oracle module:
- http://docs.codehaus.org/display/GEOTOOLS/Oracle
This one has a bonus, the page includes both the GeoServer and uDig
issues. Now these are not your responsibility to fix, but it will help
us detect problems in the field. I also tried to make it clear that
you are not responsible for fixing issues, only making sure they get
looked at, or are marked as wont fix etc... The page also includes
some outlines of our recent devel conversations with respect to use of
sdoapi.
I will go through the issues with you on the next email (on the
geotools list).
- GEOT-704 <http://jira.codehaus.org/browse/GEOT-704> TableScan
prevention - Use the Metadata <http://jira.codehaus.org/browse/GEOT-704>
we are mostly there the jira has an example, and I got a book.
- GEOT-463 <http://jira.codehaus.org/browse/GEOT-463> Update and delete
does not work correctly with database oracle 10g
<http://jira.codehaus.org/browse/GEOT-463> - no specific clue here,
update was troubled on all but a few SDO_Geometry types and as the page
indicated I have a patch.
- GEOT-361 <http://jira.codehaus.org/browse/GEOT-361> Support Views as
FeatureSource <http://jira.codehaus.org/browse/GEOT-361> - this can be
done, postgis does it, they are readonly FeatureSource as I recall
- GEOT-709 <http://jira.codehaus.org/browse/GEOT-709> Support or at
least report for old geometry fields (ake old GTYPE)
<http://jira.codehaus.org/browse/GEOT-709> - would your sdoapi jar help
here? If not WONT FIX
- GEOT-711 <http://jira.codehaus.org/browse/GEOT-711> Implement
createSchema() <http://jira.codehaus.org/browse/GEOT-711> - working on
this, and screwing it up every other time. I think my database SRID
table is messed
- GEOT-740 <http://jira.codehaus.org/browse/GEOT-740> Add support for
EPSG codes in OracleDataStore <http://jira.codehaus.org/browse/GEOT-740>
- and what is this? We do have the ability to load the EPSG database
into oracle, do we need to revese map "4326" to the best match in the
SRID table?
- GEOT-553 <http://jira.codehaus.org/browse/GEOT-553> Shapefile not
saved properly in Oracle 9i/10g
<http://jira.codehaus.org/browse/GEOT-553> Map NUMBER to Interger and
we are good?
- GEOT-744 <http://jira.codehaus.org/browse/GEOT-744> OracleDataStore
isNillable and others, not set
<http://jira.codehaus.org/browse/GEOT-744> Simple QA
- GEOT-725 <http://jira.codehaus.org/browse/GEOT-725> OracleDataStore
doesn't support temporal attributes
<http://jira.codehaus.org/browse/GEOT-725> I am adraid GeoTools does not
support temporal attributes - schedule for 2.3.x timeframe
- GEOT-729 <http://jira.codehaus.org/browse/GEOT-729> OracleDataStore
doesn't work for floats with Oracle before 10.x
<http://jira.codehaus.org/browse/GEOT-729>
- GEOT-724 <http://jira.codehaus.org/browse/GEOT-724>
org.geotools.data.oracle.sdo.SDO crash for EMPTY Geometries
<http://jira.codehaus.org/browse/GEOT-724>
- GEOT-719 <http://jira.codehaus.org/browse/GEOT-719>
OracleDataStore.getTypeNames() returns non accessible tables
<http://jira.codehaus.org/browse/GEOT-719> - seems to happen when your
connection params put you in at the wrong level
- GEOT-802 <http://jira.codehaus.org/browse/GEOT-802> "No CRS for
srid.." <http://jira.codehaus.org/browse/GEOT-802> EPSG / SRID / WKT /
CoordinateReferenceSystem needs to be thought out carefully
- GEOT-826 <http://jira.codehaus.org/browse/GEOT-826> GeomtryFilter
strange behavior after reprojecting
<http://jira.codehaus.org/browse/GEOT-826>
- GEOT-743 <http://jira.codehaus.org/browse/GEOT-743> OracleDataStore
may try to determine specific Geometry types
<http://jira.codehaus.org/browse/GEOT-743>
- GEOT-714 <http://jira.codehaus.org/browse/GEOT-714> Need to support
MultiString, MulitPoint, MultiPolygon in SQLEncoderOracle
<http://jira.codehaus.org/browse/GEOT-714> - got the patch for update
need to apply, review, etc...
- GEOT-720 <http://jira.codehaus.org/browse/GEOT-720> OracleDataStore
doesn't always correctly handle mixed-case table and field names
<http://jira.codehaus.org/browse/GEOT-720> - QA check, may need some bad
example tables on our test database
A couple more from other projects look interesting:
- GEOS-402 <http://jira.codehaus.org/browse/GEOS-402> Oracle duplicate
attributeType prevents featureTypes being created
<http://jira.codehaus.org/browse/GEOS-402>
- GEOS-432 <http://jira.codehaus.org/browse/GEOS-432> limit tables to
those listed in SDO_GEOM_METADATA_TABLE
<http://jira.codehaus.org/browse/GEOS-432>
- GEOS-584 <http://jira.codehaus.org/browse/GEOS-584> Duplicate
attribute types error when adding oracle spatial layer if multiple
layers are selectable with the same name
<http://jira.codehaus.org/browse/GEOS-584>
So we have some work cut our for ourselves, Marc you do have some time
from myself and Justin to work on these issues, if you want to set up a
plan that is great. If not we will muddle along sending you patches for
review. Justin can you communicate your needs on the oracle module page,
and I will try and do the same.
Jody
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
