We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
SET NULL
We can issue SQL where em.flush:
em.flush
DELETE
Author
Book
books.author_id
books.author_id = NULL
books.updated_at
UPDATE books SET author = null WHERE id = ... AND updated_at = last_updated_at
updated_at
last_updated_at
Potential solution is that we issue all UPDATEs first, so that they won't be invalidated by ON DELETE behavior?
UPDATE
ON DELETE
The text was updated successfully, but these errors were encountered:
fix: Fix DELETEs bumping oplocks for UPDATEs.
d9e40c4
Fixes #591.
fix: Fix DELETEs bumping oplocks for UPDATEs. (#593)
5817469
chore(release): 1.69.1 [skip ci]
0abf24f
## [1.69.1](v1.69.0...v1.69.1) (2023-03-30) ### Bug Fixes * Fix DELETEs bumping oplocks for UPDATEs. ([#593](#593)) ([5817469](5817469)), closes [#591](#591)
🎉 This issue has been resolved in version 1.69.1 🎉
The release is available on:
v1.69.1
Your semantic-release bot 📦🚀
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
We can issue SQL where
em.flush
:DELETE
s an entity likeAuthor
Book
hasbooks.author_id
with aSET NULL
on delete actionbooks.author_id = NULL
for thisBook
books.updated_at
for thatBook
UPDATE books SET author = null WHERE id = ... AND updated_at = last_updated_at
updated_at
to not equal ourlast_updated_at
Potential solution is that we issue all
UPDATE
s first, so that they won't be invalidated byON DELETE
behavior?The text was updated successfully, but these errors were encountered: