I've had a go at fixing the problem we identified at the end of Jan, and worked around, where if you joined tables in the wrong order, then your joins disappeared from the generated sql. I've had to do this because I got to the point where we could no longer work around the problem. This identified another problem, where the joins were out of order in the generated sql, and would cause an error. So I've tried to fix that too. I'm sure that my code is horrible and will require re-writing.
I've also had a go a back porting this fix to 1.0.x on a different branch (backport-associative-fix-to-1.0.x), since the fix I did on master relied on other changes not on 1.0.1. I'll create a separate pull request for that branch.
I'd appreciate a 1.0.2 release with this functionality working soon, but until then, we'll just upload a patched version into nexus.
bendlas
commented
12 years ago
Hi,
I've had a go at fixing the problem we identified at the end of Jan, and worked around, where if you joined tables in the wrong order, then your joins disappeared from the generated sql. I've had to do this because I got to the point where we could no longer work around the problem. This identified another problem, where the joins were out of order in the generated sql, and would cause an error. So I've tried to fix that too. I'm sure that my code is horrible and will require re-writing.
I've also had a go a back porting this fix to 1.0.x on a different branch (backport-associative-fix-to-1.0.x), since the fix I did on master relied on other changes not on 1.0.1. I'll create a separate pull request for that branch.
I'd appreciate a 1.0.2 release with this functionality working soon, but until then, we'll just upload a patched version into nexus.
Many thanks, Ed