You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I have a some queries that I think are a bit complex, with a lot of nested selects etc, I upgraded 0.7.0 to version 0.12.5 (Lumen upgrade too).
I started getting a error with whereIn and notIn, where I got arguments array must contain same amount of values, this was the error message in vsprintf function.
I proceed to change the CacheKey.php getInAndNotInClauses method's try/catch to throw the error and figured out the bytes of the uuid is not matching and got the error that's in the stacktrace. To fix the issue according to https://uuid.ramsey.dev/en/stable/database.html#storing-as-bytes to generate a Uuid it's using $uuid = Uuid::uuid4(); (version 4) so by changing the line where we get the subquery from bytes to $subquery = Uuid::uuid4()->fromBytes($subquery) seemed to work fine. I still wonder though if this is the right way and if so a fix to version for Lumen 9 could be created or if I should update something in my Application.
Eloquent Query
Please provide the complete eloquent query that caused the bug, for example:
Describe the bug
I have a some queries that I think are a bit complex, with a lot of nested selects etc, I upgraded 0.7.0 to version 0.12.5 (Lumen upgrade too).
I started getting a error with whereIn and notIn, where I got arguments array must contain same amount of values, this was the error message in vsprintf function.
I proceed to change the CacheKey.php
getInAndNotInClauses
method's try/catch to throw the error and figured out the bytes of the uuid is not matching and got the error that's in the stacktrace. To fix the issue according to https://uuid.ramsey.dev/en/stable/database.html#storing-as-bytes to generate a Uuid it's using$uuid = Uuid::uuid4();
(version 4) so by changing the line where we get the subquery from bytes to$subquery = Uuid::uuid4()->fromBytes($subquery)
seemed to work fine. I still wonder though if this is the right way and if so a fix to version for Lumen 9 could be created or if I should update something in my Application.Eloquent Query
Please provide the complete eloquent query that caused the bug, for example:
Note: The query is much bigger then this, that's why I need Laravel Model Caching :D
Stack Trace
Environment
Additional context
I'm using lumen-framework and not a Laravel full project and on previous version (0.7.0) this was not occurring
The text was updated successfully, but these errors were encountered: