LINQ to BigQuery's concept

concept.txt

LINQ to BigQuery's concept and mention of following tree.
https://github.com/neuecc/LINQ-to-BigQuery
https://twitter.com/headinthebox/status/539169524999012354

IQueryable isn't necessary for LINQ to translate SQL.
I need all BigQuery's sql can write LINQ to BigQuery.
All specialized sql can execute, all function can execute(include window function).
(BigQuery's SQL different with standard Sql https://developers.google.com/bigquery/query-reference
 I must support Multiple FROM, WITHIN, JOIN EACH, GROUP EACH BY, FLATTEN, IGNORECASE, etc)

Therefore control order, protect runtime error, satisfy all syntax.
"IQueryable is all database's abastraction" is fantasy,
LINQ needs specialized each Database.
(But LINQ to Xxx needs LINQ's atmosphere
 filter as Where, projection as Select, order as OrderBy/ThenBy, like convention over configuration)

I think "IQueryable is dead, Long live Expression".
Of course Expression Tree has performance issue, I don't use LINQ for RDBMS(I use Dapper).
But execute BigQuery is very expensive so LINQ to BigQuery can ignore cost of Experssion relatively.