Przemek Denkiewicz

Actually it will also resolve https://github.com/trinodb/trino-python-client/issues/95 which is pretty painful since a user needs to run `fetchone` or `fetchall` to get an error message from DDL, UPDATE and INSERT queries....

This is a library that we are looking for http://labix.org/python-dateutil#head-5fb12f4538c5a2fd83f87eea8e6c0ddd47f8b4b0

@subbareddydagumati I cannot reproduce this issue, could you please check if you still encounter this with newest Trino and trino-python-client version? Eventually could you please guide me how to reproduce...

Bumping a version is one thing which is non automated and requires manual work. Can it still be done manually, or do you prefer to have it automated? If yes,...

Discussed offline with @hashhar and I added an automation in release workflow which increments a version of trino-python-client and push bump commit before doing a release.

Workflow structure changed, I converted it to a single job workflow with multiple steps.

@hashhar PTAL

@prgx-aeveri01 would you like to open a PR to fix incremental macro? Your snippet looks like a fix for the issue.

That's an error you are getting: ``` 08:45:38 Runtime Error in model dim_order_dates_custom_schema (models/marts/core/dim_order_dates_custom_schema.sql) 08:45:38 TrinoUserError(type=USER_ERROR, name=TABLE_NOT_FOUND, message="line 2:30: Table 'memory.default.dim_order_dates_custom_schema__dbt_tmp' does not exist", query_id=20220414_084538_00215_pyttn) ```

try to create a network using `docker network create dbt-net`, perhaps clean networks before using `docker network prune -f`