[ ] output of a dry run could be custom Deno code which would be specific to the workflow and SQL and then executed in memory or saved to disk for later execution (almost like a compile option). The benefit of this approach is that it would allow run Deno test, lint, doc, coverage, etc. on the generated code.
To aid in documentation and related comprehension tasks, add a dry run option to
IngestEngine
so that it can generate SQL but not execute it.compile
option). The benefit of this approach is that it would allow run Deno test, lint, doc, coverage, etc. on the generated code.