-
-
Notifications
You must be signed in to change notification settings - Fork 27
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
joinWith and with using onCondition has problem with eager or lazy #44
Comments
also I found |
Is there any reason why you're not using: $failures = Failure::find()
->andWhere(['failure.reason' => 1])
->joinWith(['job'])
->all(); ? |
@rob006 because as I said I want all failures and the job (but I need the job only if failure has reason). it will gives the failures have reason not all failures |
It would be grate if andOnCondition and OnCondition had another param that indicate the scope of condition (in join as a general condition or in joined table which is considered by default and really useful in most of the times) |
What steps will reproduce the problem?
I want select all failures with related job only if it has a reason on failure table and I use this
Error
SQLSTATE[42S22]: Column not found: 1054 Unknown column 'failure.reason' in 'where clause'
SELECT * FROM
job
WHERE (job_id
=2) AND (failure
.reason
=1)Additional info
I have used (with) and (joinWith) also used (true and false) as second param to indicate eager or lazy and always get same error
The text was updated successfully, but these errors were encountered: