有什么解决的和未解决的SQL这里提到的区别:
考虑此查询:
SELECT * FROM dataset.view1 JOIN dataset.view2 USING (key)
其中view1
是:
SELECT 1 AS key, 'foo' AS y;
view2
是:
SELECT 1 AS key, 'bar' AS z;
在这种情况下,你能想到的解决查询作为包含JSON对象/原消息:
{
"query": "SELECT * FROM dataset.view1 JOIN dataset.view2 USING (key)"
"views":
[
{
"name": "view1",
"sql": "SELECT 1 AS key, 'foo' AS y;"
},
{
"name": "view2",
"sql": "SELECT 1 AS key, 'bar' AS z;"
}
]
}
所以,解决的查询长度是查询加上意见的长度的总和。该解决查询长度限制足够高,所以一般是不相关的标准的SQL查询。对于传统的SQL查询,不过,功能,如TABLE_DATE_RANGE
都是这样的扩展查询匹配的所有表的联合宏,所以它更容易有大解析查询大小结束。