Elias Kassell

We're not currently working on this. However, there is part of an integration checked in; the API used is missing [various features](https://github.com/dataform-co/dataform/blob/master/api/dbadapters/presto.ts), with [tests laid out here](https://github.com/dataform-co/dataform/blob/master/tests/integration/presto.spec.ts).

Looks like the connection isn't set when something is called https://github.com/brianc/node-pg-cursor/blob/master/index.js

This seems to have been done now, empty pre and post ops are ignored: ```sql config { type: "table", } pre_operations { } SELECT 1 post_operations { } ``` becomes...

This is a very reasonable request, but it's complex in its implementation, because we can either: * Add a CLI option for writeDisposition, similar to how I've just made dryRun...

Note: this implementation for this is similar to the request in https://github.com/dataform-co/dataform/issues/1385, as it interacts with the API in the same way.

We're considering doing this, potentially via SQLFluff! Closing this bug however, as it's for the IDE support which does exist (though needs some maintenance).

To expand on this, I would love to see some examples of where the functionality of Javascript UDFs can't be achieved without them. Having logic computed at runtime in BigQuery...

Can you provide instructions on how we can reproduce this error please?

A more elegant solution that we have planned for this is CLI flags for `dataform.json` parameters.

Config option was not the fix, https://github.com/dataform-co/dataform/pull/1602 demonstrates however confirms that this was not an issue with Core's `dataform.json` interpretation. Will create a new PR to add these to the...