Snapping do not work for new features after save edits on oracle spatial layer

[qgib]

Author Name: Jan Lippmann (@j-lippmann)
Original Redmine Issue: 12690
Affected QGIS version: 2.8.1
Redmine category:digitising
Assignee: Jürgen Fischer

---

Snapping do not work for new features after save edits on oracle spatial

steps:

1. start editing a oracle spatial polygon layer
2. enable snapping for this layer (vertex+segment 10 pixel)
3. create a new polygon (do not save)
4. check snapping for the new polygon ( if snapmarker appear...) in my case snapping is working
5. now save the polygon (save edits...)
6. check snapping for the new polygon after saving ( snapmarker do not appear on segment or vertex) snapping is not working
7. on other "old" polygons snapping is always working

a small screencast is in the attachement.

actual master and 2.8.1 is affected and i think only oralce spatial layer

---

• qgis_snapping_bug.mp4 (Jan Lippmann)
• CREATE_GIS_TABLES.sql (Jan Lippmann)

[qgib]

Author Name: Jürgen Fischer (@jef-n)

---

• assigned_to_id removed Jürgen Fischer

[qgib]

Author Name: Giovanni Manghi (@gioman)

---

does not happen with postgis layers. Maybe a side effect of some 3rd party plugin? could you disable them and try again? thanks.

---

• status_id was changed from Open to Feedback

[qgib]

Author Name: Jan Lippmann (@j-lippmann)

---

correct. does not happen with postgis oder mssql layer. but with oracle spatial...all 3rd party plugins are disabled

i think the problem occur since the new feature "indexing data" while the first klick on "add feature" in an edit session?
debugview writes nothing distinctive...

[qgib]

Author Name: Jan Lippmann (@j-lippmann)

---

The problem there is also at point and line features.
if i restart the qgis project. snapping is working for all features (incl. new features from the previous edit session)

in the attachment is the create script of the tables.

can anybody confirm the problem?

thanks.
jan

---

• 8655 was configured as CREATE_GIS_TABLES.sql

---

• CREATE_GIS_TABLES.sql (Jan Lippmann)

[qgib]

Author Name: Giovanni Manghi (@gioman)

---

was this an issue on previous qgis releases?

[qgib]

Author Name: Jan Lippmann (@j-lippmann)

---

my tests:
in qgis 2.2 this was no issue
in qgis 2.4 this was no issue
in qgis 2.6 this was no issue

[qgib]

Author Name: Giovanni Manghi (@gioman)

---

• status_id was changed from Feedback to Open
• priority_id was changed from Normal to Severe/Regression

[qgib]

Author Name: Jürgen Fischer (@jef-n)

---

• fixed_version_id was changed from Version 2.8.2 to Future Release - High Priority

[qgib]

Author Name: Jürgen Fischer (@jef-n)

---

Not reproducable in master or 2.8.2

---

• priority_id was changed from Severe/Regression to Normal
• status_id was changed from Open to Feedback

[qgib]

Author Name: Jürgen Fischer (@jef-n)

---

• status_id was changed from Feedback to Closed
• resolution was changed from to worksforme

[qgib]

Author Name: Jan Lippmann (@j-lippmann)

---

Hello Jürgen, there is still a problem in my environment. what else can I check? have you tested the sample tables " CREATE_GIS_TABLES.sql"?

Thank you

---

• assigned_to_id was configured as Jürgen Fischer
• status_id was changed from Closed to Reopened

[qgib]

Author Name: Jürgen Fischer (@jef-n)

---

Jan Lippmann wrote:

have you tested the sample tables " CREATE_GIS_TABLES.sql"?

Sure. Although stripped down a bit:

CREATE TABLE GIS_GRUEN_P(GID NUMBER(8, 0) DEFAULT 0 NOT NULL PRIMARY KEY, GEO_ID NUMBER(8, 0) DEFAULT 0, THE_GEOM MDSYS.SDO_GEOMETRY);
INSERT INTO MDSYS.USER_SDO_GEOM_METADATA (TABLE_NAME,COLUMN_NAME,DIMINFO,SRID) VALUES (
  'GIS_GRUEN_P','THE_GEOM',
  MDSYS.SDO_DIM_ARRAY(MDSYS.SDO_DIM_ELEMENT('X',-2147483648,2147483647,0.00005),MDSYS.SDO_DIM_ELEMENT('Y',-2147483648,2147483647,0.00005)),
  25832
);
CREATE INDEX GIS_GRUEN_P_THE_GEOM_IDX ON GIS_GRUEN_P(THE_GEOM) INDEXTYPE IS MDSYS.SPATIAL_INDEX;

CREATE TABLE GIS_GRUEN_L(GID NUMBER(8, 0) DEFAULT 0 NOT NULL PRIMARY KEY, GEO_ID NUMBER(8, 0) DEFAULT 0, THE_GEOM MDSYS.SDO_GEOMETRY);
INSERT INTO MDSYS.USER_SDO_GEOM_METADATA (TABLE_NAME,COLUMN_NAME,DIMINFO,SRID) VALUES ( 
  'GIS_GRUEN_L', 'THE_GEOM',
  MDSYS.SDO_DIM_ARRAY(MDSYS.SDO_DIM_ELEMENT('X',-2147483648,2147483647,0.00005),MDSYS.SDO_DIM_ELEMENT('Y',-2147483648,2147483647,0.00005)),
  25832
);
CREATE INDEX GIS_GRUEN_L_THE_GEOM_IDX ON GIS_GRUEN_L(THE_GEOM) INDEXTYPE IS MDSYS.SPATIAL_INDEX;

CREATE  TABLE GIS_GRUEN_F(GID NUMBER(8, 0) DEFAULT 0 NOT NULL PRIMARY KEY,GEO_ID NUMBER(8, 0) DEFAULT 0, THE_GEOM MDSYS.SDO_GEOMETRY);
INSERT INTO MDSYS.USER_SDO_GEOM_METADATA (TABLE_NAME,COLUMN_NAME,DIMINFO,SRID) VALUES ( 
  'GIS_GRUEN_F', 'THE_GEOM',
  MDSYS.SDO_DIM_ARRAY(MDSYS.SDO_DIM_ELEMENT('X',-2147483648,2147483647,0.00005),MDSYS.SDO_DIM_ELEMENT('Y',-2147483648,2147483647,0.00005)),
  25832
);
CREATE INDEX GIS_GRUEN_F_THE_GEOM_IDX ON GIS_GRUEN_F(THE_GEOM) INDEXTYPE IS MDSYS.SPATIAL_INDEX;

Not that I left out the unused sequences - I guess you left out the triggers that make use of them. That's probably also the reason why you can save without explicitly assigning unique ids. Maybe that also interfered with the geometries cached for snapping.

---

• status_id was changed from Reopened to Feedback

[qgib]

Author Name: Jürgen Fischer (@jef-n)

---

Fixed in changeset "d3df4edaedc9542830dba1a99ce1b20d2bdc5773".

---

• status_id was changed from Feedback to Closed

[qgib]

Author Name: Jan Lippmann (@j-lippmann)

---

The problem is solved.

Thank You Jürgen