Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add read concern configuration to Safe{} #2

Merged
merged 2 commits into from
Apr 18, 2017

Conversation

domodwyer
Copy link

@domodwyer domodwyer commented Apr 18, 2017

Allows setting the read concern for queries (https://docs.mongodb.com/manual/reference/read-concern/).

Follows existing API style:

session.SetSafe(&mgo.Safe{WMode: "majority", RMode: "majority"})

Merged in development so includes #1 in the diff.

@domodwyer domodwyer self-assigned this Apr 18, 2017
@domodwyer domodwyer merged commit 3f35077 into development Apr 18, 2017
@domodwyer domodwyer deleted the feature/read-concern branch April 18, 2017 11:10
domodwyer pushed a commit that referenced this pull request Aug 3, 2018
* Add 3.6 user authenticationRestrictions

* Add struct-field comment

* Add struct-field comment #2

* Add struct-field comment #3

* Add documentation link

* Fix comment

* Fix comment #2

* add to README.md

* add to README.md #2

* add to README.md #3

* Add positive/negative authentication restrictions user test

* Use denyUser for negative test

* Correct message

* Fix error match

* Fix close on nil/closed session

* Simplify test, last change :)

* Simplify test, last change :) #2

* Simplify test, last change :) #3

* Fix := error
0987363 pushed a commit to 0987363/mgo that referenced this pull request Feb 19, 2019
libi pushed a commit to libi/mgo that referenced this pull request Dec 1, 2022
libi pushed a commit to libi/mgo that referenced this pull request Dec 1, 2022
* Add read concern configuration to Safe{}

* Fix tests
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants