Add a uniqueness constraint on the ap_url field #79
Labels
No labels
A: API
A: Backend
A: Federation
A: Front-End
A: I18N
A: Meta
A: Security
Build
C: Bug
C: Discussion
C: Enhancement
C: Feature
Compatibility
Dependency
Design
Documentation
Good first issue
Help welcome
Mobile
Rendering
S: Blocked
S: Duplicate
S: Incomplete
S: Instance specific
S: Invalid
S: Needs Voting/Discussion
S: Ready for review
Suggestion
S: Voted on Loomio
S: Wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Plume/Plume#79
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I presume what's needed here is some way to disambiguate multiple instances on a domain, right? In which case this should be simply achieved by establishing an instance-specific path prefix; i.e., assuming instance names are unique, in plume-models/src/instance.rs:
@murrayjbrown sorry for the late reply, but that's not exactly the problem here: by adding this constraint, we would be sure we never store the same activity more than once.
@BaptisteGelez This issue, then, is impropertly stated. The constraint should be placed, rather, on the uniquess of an activity identifier, which is just a part of what comprises a URL. (I had previously assumed such a basic constraint would have been implemented.)