Cory Horner ha scritto: > 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. >> >> What shall we do? At least I guess we should inform users... >> > Fair enough... > > May I have a jira, and all the goodies required to reproduce the > problem? :) > > I'd like to understand how one ends up with a null schema and if so, > what you should actually be able to accomplish with it.
Here: 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. Cheers Andrea ------------------------------------------------------------------------- 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
