Bug report #17731
Updating geometry with MariaDB is flawed
Status: | Closed | ||
---|---|---|---|
Priority: | Normal | ||
Assignee: | - | ||
Category: | Data Provider | ||
Affected QGIS version: | 2.18.7 | Regression?: | No |
Operating System: | Windows 7 | Easy fix?: | No |
Pull Request or Patch supplied: | No | Resolution: | no timely feedback |
Crashes QGIS or corrupts data: | No | Copied to github as #: | 25627 |
Description
When I alter an existing geometry (ie a polygon) stored in MariaDB 10.2 in QGIS, the actual SQL done is first a delete (delete from gisdata where id = 1) and then an insert ( insert into gisdata (...)) rather than an update (update gisdata set geom = ...... where id = 1). This can cause issues for tables with foreign key constratins. There may be something special regarding the MariaDB because MySql doesn´t behave this way
Regards
Kaare
History
#1 Updated by Jürgen Fischer almost 6 years ago
- Status changed from Open to Feedback
Please test with QGIS 3.4 - QGIS 2.18 reached it's end of life.
#2 Updated by Giovanni Manghi almost 6 years ago
- Resolution set to no timely feedback
- Status changed from Feedback to Closed