-
-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
Document.populate & Document.execPopulate in a transaction #6754
Labels
confirmed-bug
We've confirmed this is a bug in Mongoose and will fix it.
enhancement
This issue is a user-facing general improvement that doesn't fix a bug or add a new feature
Milestone
Comments
Yes it will, we missed that. Thanks for pointing out this issue, we will fix ASAP 👍 |
vkarpov15
added a commit
that referenced
this issue
Jul 27, 2018
Fixed in master, will be released in 5.2.6 next Monday 👍 |
That's great, thank you @vkarpov15 🙂 Just noticed one thing: // Use `$session()` by default if the document has an associated session
// See gh-6754
if (this.$session() != null) {
const session = this.$session();
paths.forEach(path => {
path.options = path.options || {};
path.options.session = session;
});
} It means that |
You're right, good catch, will fix 👍 |
vkarpov15
added a commit
that referenced
this issue
Jul 29, 2018
vkarpov15
added a commit
that referenced
this issue
Jul 29, 2018
vkarpov15
added a commit
that referenced
this issue
Jul 29, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
confirmed-bug
We've confirmed this is a bug in Mongoose and will fix it.
enhancement
This issue is a user-facing general improvement that doesn't fix a bug or add a new feature
Docs for
doc.$session()
only mention that it appliessave()
:Does it mean that calling
doc.populate()
ordoc.execPopulate
will ignore the associated mongo session?The text was updated successfully, but these errors were encountered: