Skip to content

Waypoint import is broken #464

@mbethke

Description

@mbethke

When importing a trail with a few hundred waypoints I got "error saving trail" in the GUI.
PocketBase logs show an error inserting waypoints:

{
  "data": {
    "id": "Value must be unique"
  },
  "raw": "id: Value must be unique."
}

I'm not sure how IDs are assigned— typically they'd be automatically assigned by the DB engine but I don't think that can be the case here?
Checking the table reveals a whole bunch of already imported waypoints. I think they should have a forgein key linking them to the trail and/or be inserted in a single transaction so waypoint leftovers not connected to a trail can't happen.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions