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

feat(core): allow persisting 1:m collections #686

Merged
merged 1 commit into from Jul 26, 2020
Merged

feat(core): allow persisting 1:m collections #686

merged 1 commit into from Jul 26, 2020

Conversation

B4nan
Copy link
Member

@B4nan B4nan commented Jul 26, 2020

Previously only initialized items were allowed to be persisted when adding to
1:m collection, due to how propagation works. With this change we now allow
having inverse side collections dirty as well, firing single update query
for those if we see the items are now initialized.

Closes #467

Previously only initialized items were allowed to be persisted when adding to
1:m collection, due to how propagation works. With this change we now allow
having inverse side collections dirty as well, firing single update query
for those if we see the items are now initialized.

Closes #467
@B4nan B4nan merged commit 0a95c6e into dev Jul 26, 2020
@B4nan B4nan deleted the gh-467 branch July 26, 2020 19:17
B4nan added a commit that referenced this pull request Aug 2, 2020
Previously only initialized items were allowed to be persisted when adding to
1:m collection, due to how propagation works. With this change we now allow
having inverse side collections dirty as well, firing single update query
for those if we see the items are now initialized.

Closes #467
B4nan added a commit that referenced this pull request Aug 9, 2020
Previously only initialized items were allowed to be persisted when adding to
1:m collection, due to how propagation works. With this change we now allow
having inverse side collections dirty as well, firing single update query
for those if we see the items are now initialized.

Closes #467
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

1 participant