Open landryb opened 8 years ago
As a hackish' workaround i tried making the spatialindex table use hibernate_sequence
instead of its own spatialindex_fid_seq
. hoping that lastval would be 'more' defined within JDBC interactions
alter table spatialindex alter column fid set default nextval('hibernate_sequence');
But that didnt solve the issue, the exception is still trigerred for each MD when reindexing. Weird thing is that spatialindex table still seems correctly populated with features/bbox...
The fix seems to be in geotools since 12.x branch.
unsurprisingly, bumping geotools.version to 12.5 in pom.xml fails to build veeery quickly.
So, when we update geotools is this going to be fixed?
In an ideal world, maybe
When storing the spatialindex in postgis, when reindexing all MD a traceback is trigerred for each metadata in the log:
Afaik, this looks like http://osgeo-org.1560.x6.nabble.com/Postgis-datastore-and-lastval-request-td4978586.html / http://osgeo-org.1560.x6.nabble.com/PostGIS-JDBC-issue-with-sequences-td5190922.html which should be fixed by https://github.com/geotools/geotools/pull/759 but geonetwork uses a wayy too old geotools to try to backport this or update geotools without side-effects.