What happens?

Hi,

This is a follow up from #16839, which was fixed in #16899.

Unfortunately, it seems the issue was only fixed one way. That is, after running

set disable_timestamptz_casts to true

this

select cast('2020-01-01T15:00:00'::timestamp as timestamptz)

correctly throws an error, whereas

select cast('2020-01-01T15:00:00+0000'::timestamptz as timestamp)

does not.

Also, sidenote, this new configuration parameter does not show up in the documentation: https://duckdb.org/docs/stable/configuration/overview.

To Reproduce

See description.

OS:

Linux

DuckDB Version:

1.3.0

DuckDB Client:

Python

Hardware:

No response

Full Name:

Jakob Stigenberg

Affiliation:

Qubos Systematic

What is the latest build you tested with? If possible, we recommend testing with the latest nightly build.

I have tested with a stable release

Did you include all relevant data sets for reproducing the issue?

Not applicable - the reproduction does not require a data set

Did you include all code required to reproduce the issue?

• Yes, I have

Did you include all relevant configuration (e.g., CPU architecture, Python version, Linux distribution) to reproduce the issue?

• Yes, I have