I've run into an issue where importing userpoints fails when you try to import a second csv. The first works fine, but any imports attempted afterwards always fail. Exiting and restarting LNM will allow ONE userpoint file to be imported, then it starts failing again.

The failure message is: Caught Exception. Unique constraint failed: userdata.userdata_id Unable to fetch row. void atools::sql::SqlQuery::exec(): Error executing query.

This might be an error in the undo/redo tables that was introduced in one of the recent versions. It is already fixed since 2.8.8 but the data corruption might remain.

But it is easy to fix:

1. Export all userpoint data to CSV in "Userpoints" -> "Export as CSV". Deselect "Export selected only" or leave it as is if the button is grayed out.
2. Quit LNM
3. Delete the file "C:\Users\YOURUSERNAME\AppData\Roaming\ABarthel\little_navmap_db\little_navmap_userdata.sqlite"
4. Start LNM again and import the previously export CSV again.

This should fix the error.

Alex

 

And BTW: Use the latest LNM 2.8.12.

No joy. I deleted the userpoints, exited LNM, deleted the userdata.sqlite file, and restarted LNM (on version 2.8.12 64 bit). The first userpoints file imports fine, subsequent files fail with the Caught Exception error.

Now I see the issue too. A second import to a clean database fails. Bug. 🙁

You can workaround this if you restart LNM before importing the second set. Hope this helps.

Alex

Hi,

I use the export/import during scenery testing.

This workaround seems to work.

Is there a plan to "fix" this bug for the next version?

11 hours ago, canuck21a said:

Is there a plan to "fix" this bug for the next version?

Absolutely. It's already fixed here internally but there's more on my to do list before releasing.

Alex