-
Notifications
You must be signed in to change notification settings - Fork 586
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
Support nested transactions #49
Labels
Comments
This is blocked on core support for nested transactions. |
appden
pushed a commit
that referenced
this issue
Jun 1, 2016
Build both dynamic and static libraries of the object store
Manual transaction can help a little here. But we don't have plans for nested transactions in core. |
This was referenced Mar 15, 2024
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This is a common pattern with most databases. Right now, methods that do mutations generally shouldn't call
realm.write()
because you may which to call multiple mutating methods all inside a single transaction. When the codebases get larger, this maybe be difficult to manage without nested transaction support.The text was updated successfully, but these errors were encountered: