[Bug] tuple.index(x): x not in tuple

[drewbanin]

Issue

Issue description

On BigQuery, calls to execute with fetch=True that return nested/repeated records fail with the error tuple.index(x): x not in tuple. This happens because Agate coerces a nested field like {"col": [1,2,3]} into a table like

col.0	col.1	col.2
1	2	3

When dbt tries to call table.select(columns) on the Agate table (in order to re-order the column as specified in the query, Agate raises an exception because select(['col']) is provided, but there is no such Column in the Agate table.

This code path occurs primarily in calls to the rpc server.

dbt version: >= 0.14.0

Possible Approaches:

• don't try to reorder columns with select
• flatten out the BQ table results before suppling them to Agate
• stringify nested/repeated records (bad)

[drewbanin]

fixed in #1638