Andrea Aime wrote: >>> today we discovered that there are backward compatibility >>> issues in the postgis datastore used in geoserver 1.4.0 >>> compared to the one used in geoserver 1.3.2. >>> >>> We traced the issue to "geometry_columns" having no schema >>> information, coupled with changed occurred on 2.2.x at >>> revision revisions 20520 and 20512 by chorner >>> referring to http://jira.codehaus.org/browse/GEOT-377. >>> >>> Basically the datastore does not work anymore if you have >>> null schemas. >>> >>> Now, the new AddGeometryColumn function fills in schema information, >>> so our dataset has been probably created by other means, or >>> set up by an older AddGeometryColumn. >>> > > http://jira.codehaus.org/browse/GEOT-1022 > > The goodies required are just a postgis datastore where you nullify > the f_table_schema colum for at least one table.
Ok... i'm putting together a patch to attach to this bug (not sure what the commit allowance of 2.2.x is). I've written some online tests for setting up postgis tables to test the following conditions: - no geometry column record - f_table_schema = '' - f_table_schema = 'public' - srid = -1 Rather than tossing an exception right away, i've added some additional checks in the PostgisDataStore.getGeometryAttribute and PostgisDataStore.determineSRID to grab the first feature and get its geom/crs iff the geometry_columns lookup fails. Thoughts? Cheers, Cory. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
