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

Support nested transactions #49

Closed
appden opened this issue Oct 12, 2015 · 2 comments
Closed

Support nested transactions #49

appden opened this issue Oct 12, 2015 · 2 comments

Comments

@appden
Copy link
Contributor

appden commented Oct 12, 2015

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.

@alazier
Copy link
Contributor

alazier commented Oct 12, 2015

This is blocked on core support for nested transactions.

@alazier alazier added the P2 label Oct 12, 2015
@alazier alazier added backlog and removed P2 labels Nov 16, 2015
appden pushed a commit that referenced this issue Jun 1, 2016
Build both dynamic and static libraries of the object store
alazier pushed a commit that referenced this issue Sep 14, 2016
Added jenkinsfile for building RPMs
@bmunkholm bmunkholm added Blocked This issue is blocked by another issue and removed Blocked On Core labels May 18, 2017
@RealmBot RealmBot changed the title Support nested transactions Support nested transactions Nov 12, 2019
@kneth
Copy link
Contributor

kneth commented Feb 25, 2020

Manual transaction can help a little here. But we don't have plans for nested transactions in core.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants