-
Notifications
You must be signed in to change notification settings - Fork 2.5k
Merge 3.6.x up into 4.0.x #12092
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
Merged
Merged
Merge 3.6.x up into 4.0.x #12092
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
3.5.0 has been released. - 3.6.x is the new upcoming branch; - 3.5.x is now the current branch; - 3.4.x is no longer maintained.
That method has been deprecated for almost 15 years, in 85d4084. On top of that I'm adding a deprecation for something related that was scheduled for deprecation at in the same commit.
Update branch metadata for 3.5.0
Stop using QueryBuilder::getRootAlias()
Since doctrine/doctrine-website#372, they are no longer necessary, it's possible to rely on tags. Once this is merged, the branches can be removed.
Remove branchName from unmaintained branch
Add proper handling for binary primary key parameter types that were previously causing runtime exceptions. The existing parameter type switch statement was missing a case for binary types, leading to unhandled scenarios when working with binary primary keys. This ensures consistent parameter type handling across all supported primary key data types in the ORM.
Co-authored-by: Grégoire Paris <postmaster@greg0ire.fr>
…-reupload Fix unhandled ParameterType case for binary PKs
This fixes a dangerous bug where LIMIT is silently ignored in DELETE operations, potentially causing developers to delete all rows instead of just the intended subset. The setMaxResults() method would be silently omitted from the final query, making operations like delete last entry accidentally delete entire tables.
This should fix the build. Maybe some of the reported issues can be addressed, but if that is the case, it should probably be done on the next minor branch.
Update baseline because of doctrine/dbal 4.3.0
…misuse QueryBuilder: prevent misuse of DELETE with LIMIT
Merge 3.5.x up into 3.6.x
…primary identifier
Proxy class with BackedEnum as primary key does not convert the enum
📖 Actualize code block to be compatible with DBAL v4, use modern PHP
Fix embedded classes display in orm:mapping:command output
Merge 2.20.x up into 3.5.x
Merge 3.5.x up into 3.6.x
…output Add JSON format option for orm:mapping:describe command output
It is replaced with property accessors since doctrine#11659
Deprecate ClassMetadata::$reflFields
Merge 3.5.x up into 3.6.x
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.
No description provided.