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
Not sure how to best implement it. Probably it would be nicest to have the second edge overwrite the first one, because then we can update names or geometries. Though if that is hard, a no-op on the second line would also be an improvement.
The text was updated successfully, but these errors were encountered:
Let's throw an error on edge.add. Check for duplicates in a similar way to how #1717 checks for duplicate node ID adds; keep a set with the unique (from_node_id, to_node_id) keys. Best done after #1717 is merged since otherwise we also need from_node_type, to_node_type.
Currently adding the same edge twice:
will add a duplicate row to the Edge table.
Not sure how to best implement it. Probably it would be nicest to have the second edge overwrite the first one, because then we can update names or geometries. Though if that is hard, a no-op on the second line would also be an improvement.
The text was updated successfully, but these errors were encountered: