| license: gpl-3.0 | |
| height: 960 | |
| border: no |
| {%- call statement('date_range_query', fetch_result=True) -%} | |
| select | |
| min(order_date) min_date, | |
| max(order_date) max_date | |
| from {{ ref('stg_sales_data') }} | |
| {%- endcall -%} | |
| {%- set start_date = load_result('date_range_query')['data'][0][0] -%} | |
| {%- set end_date = load_result('date_range_query')['data'][0][1] -%} |
Issue resolved with 'READ_ONLY' access_mode, as per: duckdb/duckdb#7743 (comment)
This gist showcases how DuckDB on nodejs fails to with "Connection was never established or has been closed already" when running in cluster mode.
Calling (using an in :memory: database)
node cluster.js