-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[DoctrinBridge] make Uid types stricter #38605
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
Conversation
IMO, none of them should, as they change the PHP format |
b903774
to
6351197
Compare
Alright, updated. I also removed |
c7c4251
to
2d9c31d
Compare
they are required, because the type does not register a mapping type, so schema introspection would not recognize them without the special comment |
2d9c31d
to
ba31d0e
Compare
Thanks, reverted this part :) |
Thank you @nicolas-grekas. |
(Partially reverted in #38986) |
…lues (nicolas-grekas) This PR was merged into the 5.2-dev branch. Discussion ---------- [DoctrineBridge] accept converting Uid-as-strings to db-values | Q | A | ------------- | --- | Branch? | 5.2 | Bug fix? | yes | New feature? | no | Deprecations? | no | Tickets | Fix #38929 | License | MIT | Doc PR | - In #38605 I made Uid types stricter by taking inspiration from native Doctrine types. But #38929 (comment) made me realize this doesn't work with ParamConverters. Here is the fix. Commits ------- 20714d6 [DoctrineBridge] accept converting Uid-as-strings to db-values
Reviewing #38600 made me realize we don't need to deal with converting strings to db values.
We should only support converting actual
AbstractUid
instances in the DB.Also, the binary types should not extend
GuidType
.