Milton Jonathan ha scritto: > Hello people > > I heard that the OracleDataStore was now brand new and nice, so I > decided to try it out.
Which version of the OracleDataStore are you using? The new one is in the the unsupported/jdbc-ng/jdbc-oracle module. > However, I got into some trouble trying to put > some data from a shapefile into the database. This is something I still haven't tried. > So, I'd like to ask some questions: > > 1. Is Oracle still officially "unsupported" (meaning we don't get to > expect too much out of it)? Still officially unsupported, we finished the first batch of development on top of it, but yours is basically the second feedback I get about it. So far I've used it read only in my tests with GeoServer, thought there are quite a bit of write unit tests as well (cannot run the WFS cite tests because spatial disallows the usage of mixed case column names). On whether it will ever become supported, it really boils down to a couple of options: - it drives enough business to justify keep working on it - someone else takes maintainership of it (possibly someone that has a stake in it, that is, that depends on the datastore to be working for his work) I cannot really imagine anyone working on Oracle for free, just for the pleasure of it ;) Up until then I'll be eager to do some limited bug fixing, but no more than that. > 2. I'm using geotools 2.5-SNAPSHOT, is that really the recommended place > for trying out things with Oracle? > > 3. Just to make sure: is this the correct maven pom snippet to use? > <dependency> > <groupId>ojdbc</groupId> > <artifactId>ojdbc</artifactId> > <version>14</version> > </dependency> Hum.... not unless you hand installed the driver with those params. The Oracle JDBC drivers are distributed under a click through license so they cannot be included in the official maven repositories. > 4. If everything I did was correct, then.. I ended up finding some > issues and couldn't get things to work: > > 4.1 It always fails when I try to create a table (e.g., when creating a > schema) that has String (VARCHAR) columns. Actually, we tracked it down > to the class org.geotools.data.oracle.SqlStatementEnconder, which simply > translates Strings to VARCHAR. But Oracle seems to require a size > parameter, only accepting SQL statements with something like > VARCHAR(10), etc. It may also be a good idea to use VARCHAR2, since that > is what Oracle recommends. Anyway: am I missing something or is this > really happening to everybody else? Hmmm... there is a unit test that does create a schema with strings and it's working? Can you open a jira issue at attach the shapefile you're using as well as the code? > 4.2 After solving that we were able to create a schema and see tables > being created OK in the Oracle database. However, we still got into some > trouble: although everything seems to be there, we keep getting a > SchemaNotFoundException when trying to get the FeatureSource back, I > don't know exactly why. Even stranger, calling > OracleDataStore.getTypeNames() gives me back 4292 (!) type names even > for an empty DataStore (4293 after the successful creation of a schema). > Any ideas? Yeah, we still haven't ported the table name filters from the old datastore, so you're getting back the full list of tables that the jdbc driver is reporting in the database metadata objects. Can you open an improvement request for that as well? Cheers Andrea -- Andrea Aime OpenGeo - http://opengeo.org Expert service straight from the developers. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Geotools-gt2-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
