-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UPDATE3 Trigger needs to be reviewed #414
Comments
@rouault What do you think? |
If we confirm this is an issue, this would be a good reason to issue a GeoPackage corrigendum. The ETS would be updated so that 1.2.0 and older work on either version of the trigger and 1.2.1 and later require the updated version. |
@jyutzler I fully agree with Keith's finding. I could reproduce an issue with the initial trigger SQL, and it was fixed with Keith's changes. Just fixed it accordingly in OGR. |
… in opengeospatial/geopackage#414 git-svn-id: https://svn.osgeo.org/gdal/branches/2.2@41766 f0d54148-0727-0410-94bb-9a71ac55c965
… in opengeospatial/geopackage#414 git-svn-id: https://svn.osgeo.org/gdal/trunk@41765 f0d54148-0727-0410-94bb-9a71ac55c965
… in opengeospatial/geopackage#414 git-svn-id: https://svn.osgeo.org/gdal/trunk/gdal@41765 f0d54148-0727-0410-94bb-9a71ac55c965
#414 removing erroneous part of trigger
The update3 trigger needs to have the “of ” portion (in yellow below) struck. As written the update3 trigger will only fire when the geometry is actually updated because of the “of ” clause – the key action this trigger is designed to handle is when the ID is changed – it can also deal with a geometry change at the same time – but as written will not fire if only the ID is changed.
This has not surfaced in the field because most SQLite applications never change the internal id value of an existing row. This would be hard to debug in the field…
The text was updated successfully, but these errors were encountered: