-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
[BUG]: undefined column with columnMap and model caching #16420
Labels
Comments
hi @Deathamns, I think I have detected the bug, trying to replicate it in the tests, a fix will be issued soon. |
@Deathamns just to confirm, are you using APCU or any other cache metadata? |
I had the |
rudiservo
added a commit
to rudiservo/cphalcon
that referenced
this issue
Sep 1, 2023
5 tasks
niden
added a commit
that referenced
this issue
Sep 5, 2023
Fix #16420, fixed metadata get column from cache adapters, added tests
Resolved in #16421 Thank you @Deathamns and @rudiservo |
niden
added
status: medium
Medium
5.0
The issues we want to solve in the 5.0 release
and removed
status: unverified
Unverified
labels
Sep 5, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Describe the bug
modelsMetadata
andcolumnMap
don't work well together since v5.3.0. In v5.2.3 everything was fine.The following script runs at first time, and its output should be
1
.After creating the models' cache, every following execution will result in an error:
Column 'user_id' doesn't belong to any of the selected models (1), when preparing: SELECT user_id FROM Users
Deleting the cache directory allows the script to run correctly once more.
Removing the
$di->setShared('modelsMetadata', ...);
part or not usingcolumnMap
"solves" the problem.Possible culprit #16393.
Maybe related #16411, but I'm not sure.
To Reproduce
Expected behavior
Print
1
every time the script is executed.Details
The text was updated successfully, but these errors were encountered: