Skip to content
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.

Browse node shows wrong relation #4092

Closed
openstreetmap-trac opened this issue Jul 23, 2021 · 2 comments
Closed

Browse node shows wrong relation #4092

openstreetmap-trac opened this issue Jul 23, 2021 · 2 comments
Assignees
@openstreetmap-trac
Labels
Component: website Priority: minor Resolution: fixed Type: defect

Comments

@openstreetmap-trac
Copy link

Reporter: Zartbitter
[Submitted to the original trac issue database at 7.41pm, Thursday, 17th November 2011]

Look at http://www.openstreetmap.org/browse/node/25230425
It says the node is member of two relations. One is correct (turn restriction 1650366). One is not correct (relation 81686).
Looking at relation 81686: there is a member way with id 25230425.

Maybe at browse node you're joining the id without looking at the type (way/node).
@openstreetmap-trac openstreetmap-trac self-assigned this Jul 23, 2021
@openstreetmap-trac
Copy link
Author

Author: TomH
[Added to the original trac issue at 10.18am, Friday, 18th November 2011]

This is an issue with composite primary keys and polymorphic relationships. I've fixed it in the composite_primary_keys plugin and opened a pull request to get it upstream:

composite-primary-keys/composite_primary_keys#76

@openstreetmap-trac
Copy link
Author

Author: TomH
[Added to the original trac issue at 10.26am, Friday, 18th November 2011]

I have monkey patched the fix into our code until we get a new upstream release, and the fix should deploy shortly.

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

@openstreetmap-trac openstreetmap-trac

Labels
Component: website Priority: minor Resolution: fixed Type: defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@openstreetmap-trac