You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently if a column is included in the where or select clause but the associated table is not included in the from() then sql is still produced referencing the column as if it had been included. Which can produce very cryptic error messages that are hard to track down the source of.
This is particularly likely if an extractor written for one query is reused for another similar query but with some tables omitted , say.
It would be good to have an error or warning that highlights if a column is being used without the associated table
The text was updated successfully, but these errors were encountered:
@brendanator, do you think we could potentially solve this with a solution like lihaoyi/scala.rx@4cb66a3? (The RxCtx that tracks the dependencies of the current code block)
I think potentially extractor.flatMap could be implemented with this pattern too?
Currently if a column is included in the where or select clause but the associated table is not included in the from() then sql is still produced referencing the column as if it had been included. Which can produce very cryptic error messages that are hard to track down the source of.
This is particularly likely if an extractor written for one query is reused for another similar query but with some tables omitted , say.
It would be good to have an error or warning that highlights if a column is being used without the associated table
The text was updated successfully, but these errors were encountered: