Skip to content

Commit 197cf66

Browse files
adwk67claude
andcommitted
docs: note that incremental-refresh bounds follow the session time zone
For a timestamp with time zone column, Power BI sends RangeStart and RangeEnd as plain TIMESTAMP literals, which Trino interprets in the session time zone. Partition boundaries therefore move if TimeZone changes on a dataset that already has partitions. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
1 parent c7c0b81 commit 197cf66

1 file changed

Lines changed: 5 additions & 0 deletions

File tree

‎README.md‎

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -78,6 +78,11 @@ proper entry in the **Get Data** dialog instead of the generic ODBC one.
7878
2. In **File > Options > Security**, allow any extension to load.
7979
3. Restart Power BI Desktop. **Stackable Trino** now appears under **Get Data**.
8080

81+
For incremental refresh on a `timestamp with time zone` column, Trino compares
82+
the `RangeStart` and `RangeEnd` bounds in the session time zone (`TimeZone`),
83+
so partition boundaries follow that zone. Changing `TimeZone` on a dataset that
84+
already has partitions moves the boundaries.
85+
8186
### Your first query
8287

8388
Assuming a Trino instance is reachable on the given host and port:

0 commit comments

Comments
 (0)