Add some constraint at database level #342
No reviewers
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
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Plume/Plume#342
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "db-constraints"
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?
Fixes #79 and should fix #201 and #113 as well
valueofApiTokenis uniqueThere is some issue with migrating on an instance that don't currently met the constrain, I'm getting a
could not create unique index "blog_unique"because I've some duplicated blogs (I think those are old tests leaks in my case, but as some will have some constraint violated, we should make sure the migration goes smoothly)For postgresql this can be done with queries such as
run before applying constrains, however this might lead to other data being deleted (things referencing a duplicate instead of the first entry)
This constrain seems to forbid from having more than one remote medias (it allows for only one null)
Codecov Report
40.17% <100%> (-0.15%)59.4% <100%> (+4.02%)98.16% <100%> (ø)53.95% <80%> (-0.68%)0% <0%> (ø)Continue to review full report at Codecov.
works fine on postgresql. I assume you tested sqlite by yourself
this constraint won't exist (won't fail because drop if exists, but also useless)