Blog Post: ORM 3.4 released #750
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
greg0ire
reviewed
Jun 22, 2025
greg0ire
reviewed
Jun 22, 2025
greg0ire
reviewed
Jun 22, 2025
greg0ire
reviewed
Jun 22, 2025
Co-authored-by: Grégoire Paris <[email protected]>
greg0ire
approved these changes
Jun 23, 2025
stof
reviewed
Jun 23, 2025
| With the re-adding of PARTIAL queries, the move towards native lazy objects | ||
| the only deprecation that we haven't fully addressed yet for a migration | ||
| towards 3.x is the use of an argument for `EntityManager::flush($entity)` | ||
| ([#8459](https://github.com/doctrine/orm/issues/8459)). |
There was a problem hiding this comment.
This is not true that it is the only one: doctrine/orm#9219
There was a problem hiding this comment.
Should this be mentioned in the blog post too?
derrabus
approved these changes
Jun 23, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Clarify the significance of the 3.4 release, and what it means for upgrading from 2.x