tglunde / dbt-exasol

data build tool adapter for exasol
Apache License 2.0
18 stars 12 forks source link

session datetime format set to JSON #119

Closed djamadeus closed 7 months ago

djamadeus commented 7 months ago

in incremental models when we compare dates for the incremental clause we endup with this:

Exasol Query Error: data exception - invalid character value for cast; Value: '2024-03-19 01:02:27.095000' Format: 'YYYY-MM-DDTHH:MI:SS.FF6' (Session: 1793951975412989952)

I don't understand where the 'T' in expected format comes from. is there NLS_DATE_LANGUAGE soemwhere set in the adapter?

incremental clause:

    {% if is_incremental() %}

    {%- call statement('where_pushdown_for_virtual_schema_statement', fetch_result=True) -%}
        select max(PV_TIMESTAMP) from {{ this }}
    {%- endcall -%}

    {%- set max_date = load_result('where_pushdown_for_virtual_schema_statement')['data'][0][0] -%}

  -- this filter will only be applied on an incremental run
where PV_TIMESTAMP >= '{{ max_date }}'

    {% endif %}

I can fix this then by using to_char and re-formatting the date, but I don't understand where the JSON-Notation comes (on the side of the selected PV_TIMESTAMP, not the variable) in the first place

djamadeus commented 7 months ago

my bad, just found the timestamp parameter for the connection configuration in the readme, sry