Find method dies during a `with` query in MySQL about lithium HOT 11 CLOSED

More information is needed on this as was mentioned in IRC. The All related code (Model, Query etc) must be provided to help better figure out what's going on. A dump of sample MySQL data would be helpful as well.

from lithium.

I get it also. Seems any find with associated model where the only condition is a pk of the main model that doesnt exist in the table will cause this problem.

from lithium.

Interesting. @alkemann or @davidgolding, can one of you submit a small sample of reproduce code (even if not a full test case), so we can get going on this? Just want to make sure we're fixing the right bug, and that it doesn't show up again.

Thanks, guys!

from lithium.

[paste removed, no good url] - /clients/view/1 - works fine, while any value of {:id} other than 1 will cause the sql bug

from lithium.

I was able to replicate the behavior using li3_microblog (see my github) but does not break SQLite.

A way to fix this would be to stop querying the database engine if the first query does not return any records.

from lithium.

As far as I can tell, this behavior is happening in \lithium\data\source\Database::read() around lines 282-288:

https://github.com/UnionOfRAD/lithium/blob/master/data/source/Database.php#L282-288

I may be missing where the adapter could be calling for the additional query, though.

from lithium.

https://gist.github.com/37fb48e331050cb8cae2

This is what I've used to replicate the error. Going to /posts/view/1 succeeds, but like alkemann's example, any other {:id} value that doesn't match a record in the posts table will return the SQL error.

from lithium.

Does this pull request resolve the issue?

#106

from lithium.

Yes, a test case also exists for that. Sorry I looked over this ticket.

from lithium.

@david, if you have any further issues please do let me know.

from lithium.

Fantabulous. Excellent, thanks.

from lithium.