Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 adds a query modifier for any fields that don't already have a
table.columnform.It takes the table name, or alias, from the
from()modifier and simply tacks it onto any fields that are I guess 'naked'.This applies to:
Example
produces:
Regarding conditions
It only performs this modification on the left-hand side of an expression. If the right-hand is missing the table then there's not much we can do. Or is there?
I'm not sure about string conditions either. They're quite an weird edge-case altogether.
Some testing will clarify all of this.
Draft because: