Database: SetSafe() necessary? #8
Labels
No Label
bug
change
check
Comp::Backend
Comp::Database
Comp::ICCC
Comp::Logging
Comp::Sessions
Comp::System
Comp::Users
enhancement
note
outdated
question
Ready2Test
security
todo
wontfix
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Go/Ocean#8
Loading…
Reference in New Issue
Block a user
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?
Check the default behavior of mgo's safe setting and afterwards may use SetSafe() for the session, to provide a propper mode.
There is also a EnsureSafe() function! Check the whole behavior behind this.
Done. The safe mode is set to "majority" to ensure, that the majority of all servers has acknowledged. The mode is set to "eventual" which allows to read from any secondary but write to master server.
Todo: Specify both also for the ConfigurationDB!
Done and all tests passed :)