-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
[FIX] use a nonserialized cursor for updating user groups #250
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
[FIX] use a nonserialized cursor for updating user groups #250
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Serialized=True to avoid serialized?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@moylop260 thanks so much, I messed up the only thing that was to mess up here...
|
Are you sure you don't need to serialize? How user get correct groups then? |
|
Using a nonserialized cursor doesn't always help, as the ORM also wants to update the user's |
|
@pedrobaeza the worst thing that can happen is to have not all dynamic groups, which will be fixed with the next login |
|
Is posible add a test case that reproduce the problem? |
|
difficult, because it's a timing issue with multiple users involved |
|
👍 |
1 similar comment
|
👍 |
…r_serialized [FIX] use a nonserialized cursor for updating user groups
Syncing from upstream OCA/server-tools (11.0)
Doing this in a serialized transaction can cause deadlocks, and we don't need serialization here