You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
GlobalMapper fails to open Kart GPKG working copies, with an malformed-database-schema error
After some digging, turns out GlobalMapper doesn't like this trigger:
CREATE TRIGGER _mytable_upd
AFTER UPDATE ON mytable
BEGIN
INSERT OR REPLACE INTO gpkg_kart_track (table_name, pk)
VALUES ('mytable', NEW.fid), ('mytable', OLD.fid);
END;
Specifically it doesn't understand this form of INSERT: INSERT [OR REPLACE] INTO <into> VALUES <row1>, <row2>;
If one of the rows-to-insert the trigger is removed, GlobalMapper is happy.
Presumably GlobalMapper uses a very old sqlite version that doesn't understand such things.
As a workaround, Kart could create the update trigger with two insert statements that insert one row each, instead of one trigger that inserts two rows. This has no real downsides (slightly less efficient) so we may as well.
**Version Info **
issue is in GlobalMapper 24_1-x64 for 64 bit Windows
The text was updated successfully, but these errors were encountered:
This is fixed in release 0.14.1 - if you are affected by this issue, recreate your Kart working copy using Kart 0.14.1 ie kart create-workingcopy --delete-existing
GlobalMapper fails to open Kart GPKG working copies, with an malformed-database-schema error
After some digging, turns out GlobalMapper doesn't like this trigger:
Specifically it doesn't understand this form of INSERT:
INSERT [OR REPLACE] INTO <into> VALUES <row1>, <row2>;
If one of the rows-to-insert the trigger is removed, GlobalMapper is happy.
Presumably GlobalMapper uses a very old sqlite version that doesn't understand such things.
As a workaround, Kart could create the update trigger with two insert statements that insert one row each, instead of one trigger that inserts two rows. This has no real downsides (slightly less efficient) so we may as well.
**Version Info **
The text was updated successfully, but these errors were encountered: