Skip to content

Conversation

@wonder-sk
Copy link
Contributor

Fixes #38

This could happen because we were keeping outdated entries in remap tables of work packages - the tuples (master_fid, wp_fid) would get added as needed, but they were never getting deleting when the corresponding features got deleted. As a result, users could get an error from SQLite about unique constraint violation when inserting to the remap table because the master_fid already existed there from some previous runs.

Fixes #38

This could happen because we were keeping outdated entries in remap
tables of work packages - the tuples (master_fid, wp_fid) would get
added as needed, but they were never getting deleting when the corresponding
features got deleted. As a result, users could get an error from SQLite
about unique constraint violation when inserting to the remap table
because the master_fid already existed there from some previous runs.
@wonder-sk wonder-sk added the bug Something isn't working label Aug 19, 2025
Copy link

@MarcelGeo MarcelGeo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice, as we discussed that in person - LGTM.

@wonder-sk wonder-sk merged commit 8446c2c into main Aug 19, 2025
2 checks passed

- name: Kyle_duplicate
value: 4
mergin-project: martin/farms-Kyle-duplicate
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

doens't look like good location for test files in Martin workspace :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

remap table goes out of sync

4 participants