Application exception on latest version #379
Replies: 6 comments
-
we are planning the switch to doctrine 3 and dbal 4 , in the version 5 of the API So is not tested at all with DBAL 4 . |
Beta Was this translation helpful? Give feedback.
-
Do you think it’s related? |
Beta Was this translation helpful? Give feedback.
-
@tasselchof not necessarily related, but at least the initial stack is stable ( with dbal 3) . Is a type related issue. |
Beta Was this translation helpful? Give feedback.
-
@arhimede the problem is in uuid type, I guess something about this one: https://github.com/doctrine/dbal/blob/4.0.x/UPGRADE.md#bc-break-changes-to-handling-binary-fields. |
Beta Was this translation helpful? Give feedback.
-
Better go back to DBAL 3 and play there... |
Beta Was this translation helpful? Give feedback.
-
I just fixed the types provided by Ramsey/doctrine-uuid, and they are now working with dbal version 4.0.1. However, I am not sure if this library will be updated soon enough. I mean, I can submit a pull request here, but it's obviously going to be more than just "updating the version": ramsey/uuid-doctrine#247. |
Beta Was this translation helpful? Give feedback.
-
Hi,
I encountered this exception while attempting to retrieve users from the database:
It's standard application, except I removed link to the roles (trying to build basic graphql api - to get users together with table properties for my frontend).
I am using ramsey/uuid-doctrine with dbal:4.0 though (your repo has a limitation dbal:3.0).
I'll probably figure it our myself, but if you have an idea where the issue might be I would be grateful.
Beta Was this translation helpful? Give feedback.
All reactions