-
Notifications
You must be signed in to change notification settings - Fork 11
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: Using join with Mappings causes PDO statement to become false. #18
Comments
Just had the same error but this time was caused by adding an ->eq condition to the Table object instead. Some debug info.
And this is what it gave me:
|
Update: based on the resulting SQL it appears it should have been throwing an error for an ambiguous table column reference. This is what I am using in my local copy:
|
@b-hayes @joshmcrae this should be fixed with this PR in tithely/picomapper tithely/picomapper#18 |
VERSION USED
"elvanto/picodb": "2.1.0"
What happened:
When using a mapping like so:
Fetch all works fine, but if we add a join before a fetch all:
Results in:
Note the error happens internal. I traced it to
vendor/elvanto/picodb/lib/PicoDb/StatementHandler.php:240
and added a dump of the errorsprint_r($pdoStatement->errorInfo()); die();
and saw only this:Expected I expected:
Now If I do the same thing with a Table object instead everything works as it should:
I expect the mapper to work the same.
The text was updated successfully, but these errors were encountered: