Fixes a bug where you cannot use a runtime operator in a SQL query #82
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This attempts to fix the bug documented in #40. As you stated, it wasn't a trivial fix and our fix is, unfortunately, a bit disruptive.
This introduces a few new objects to track what type of operators are being created so that they can be formatted correctly when they are written out to a cache. Breaking out of strings is a bit messy but it was the most straightforward method we could find to solve the issue.
We've only confirmed that the native and DoctrineORM targets work right now as that is what we use in our project. I'd like feedback on our approach but we do intend on fixing the other targets and tests to work.