Hi, The issue has been created and the pull request is done. Waiting for the check and the possible merge on the h2 team side:
https://github.com/h2database/h2database/pull/267 Best regards, Nicolas Fortin, Développeur d’applications - AI Laboratoire d’Acoustique Environnementale (LAE) Ifsttar Nantes, Route de Bouaye, CS 4, 44344 Bouguenais Cedex Activités du Laboratoire d’Acoustique Environnementale : www.lae.ifsttar.fr Un logiciel open-source pour l’acoustique des salles : I-Simpa ( i-simpa.ifsttar.fr) Un logiciel open-source pour des études d’impact en milieu extérieur : NoiseM@p (noisemap.orbisgis.org) Le mardi 26 avril 2016 11:02:56 UTC+2, Blaž Repnik a écrit : > > Excellent. Any info about when the patch will be commited? Thanks! > > > Dne torek, 26. april 2016 09.09.14 UTC+2 je oseba Nicolas Fortin > (OrbisGIS) napisala: >> >> Hi, >> >> Yes it seems that update on null geometry does not update the index. >> Using the following query >> >> drop table if exists DUMMY_11;CREATE TABLE PUBLIC.DUMMY_11 (fid serial, >> GEOM GEOMETRY);CREATE SPATIAL INDEX PUBLIC_DUMMY_11_SPATIAL_INDEX on >> PUBLIC.DUMMY_11(GEOM);insert into PUBLIC.DUMMY_11(geom) values(null);update >> PUBLIC.DUMMY_11 set geom = 'POLYGON((1 1,5 1,5 5,1 5,1 1))';select fid, GEOM >> from DUMMY_11 where GEOM && 'POLYGON((1 1,5 1,5 5,1 5,1 1))'; >> >> I will add this on unit test of h2 and test it. >> >> Thank you for the report. >> >> Best regards, >> >> Nicolas Fortin, >> >> Développeur d’applications - AI >> Laboratoire d’Acoustique Environnementale (LAE) >> Ifsttar Nantes, Route de Bouaye, CS 4, 44344 Bouguenais Cedex >> >> Activités du Laboratoire d’Acoustique Environnementale : >> www.lae.ifsttar.fr >> Un logiciel open-source pour l’acoustique des salles : I-Simpa ( >> i-simpa.ifsttar.fr) >> Un logiciel open-source pour des études d’impact en milieu extérieur : >> NoiseM@p (noisemap.orbisgis.org) >> >> Le lundi 25 avril 2016 16:35:11 UTC+2, Blaž Repnik a écrit : >> >> Hey! >>> >>> I have a table into which i insert records with polygonal geometry. And >>> the problem is that some records do not show in the resultset when using >>> the spatial query (&& WKT_GEOM). I checked manually that the geometry of >>> the inserted features overlaps (actually the are completely within) the >>> query geometry. If i drop the spatial index and recreate it, i get the >>> missing records! >>> >>> I was not able to produce a working example on a simple table (my table >>> has about 30 columns). But this is what i do: >>> >>> First i insert the record with null geometry, then i update the geometry >>> column with "normal" geometry. So i guess the problem lies in updating the >>> spatial index? Any ideas? >>> >>> Also, i'm using the 191 version. >>> >>> Thanks! >>> >> >> > -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
