-
Notifications
You must be signed in to change notification settings - Fork 53
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
Better log for: "Encountered empty IN condition with key id" #155
Comments
This has been present for years. I typically wrap my INs to ensure there is at least one item.
What is needed:
or
|
So just step over the case of empty condition-arrays and not do anything about it? |
My guess is that it would fix the problem if the core was changed to do a quick sanity check. |
I was just coming here to report the same issue. It would be fantastic if the error was able to report the class causing the issue (instead of just xpdoquery.class.php). Would that even be possible? |
Feature request
Summary
Sometimes I get this error in the logs:
Looking at this line:
https://github.com/modxcms/xpdo/blob/3.x/src/xPDO/Om/xPDOQuery.php#L783 or
https://github.com/modxcms/revolution/blob/2.x/core/xpdo/om/xpdoquery.class.php#L764
it doesn't even seem to be something grave - but I'd still like to find the origin of it.
That's why I would like more information on this log.
Why is it needed?
Better debugging and fixing of possible errors.
Suggested solution(s)
I would like to see the complete
$query
or also where it occurred.I thought I'd get more information by logging
$conditions
:But logging
$conditions
didn't help much:If someone can give me a hint, or a recommendation, I'd be happy to test and prepare a PR.
The text was updated successfully, but these errors were encountered: