Dave Welden

The data set used is DCSKINPRODUCT.sas7bdat from [SAS-Visual-Forecasting---sample-data-sets](https://github.com/vasepu/SAS-Visual-Forecasting---sample-data-sets/blob/master/SAS%20Visual%20Forecasting%20-%20sample%20data%20sets.zip) [DCSKINPRODUCT.zip](https://github.com/snowflakedb/snowflake-connector-python/files/12253259/DCSKINPRODUCT.zip) ``` sql -- Query Snowflake to examine the invalid dates select to_varchar("DATE") from dcskinproduct limit 20; 43113053-09-24 17:00:00.000 43132219-01-30 16:00:00.000 43151384-06-05...

For now, I have the following workaround in place, but this should not be required. ``` python # Map datetime columns to string (needed because of bug in write_pandas) for...

When will this paramter be available in Snowpark? The new parameter is not available in Snowpark for Python version 1.9.0 or 1.10.0 snowflake.snowpark.Session.write_pandas. ``` python >>> session.write_pandas(df, target_table, use_logical_type=True) Traceback...

An option to omit role and leverage the specified user's default role would also be welcome.

Is there any update on whether this issue will be resolved or closed?

This issue is resolved.


Yes I did not catch that until after posting this issue On Mar 2, 2025, at 05:23, jochenchrist ***@***.***> wrote: In your YAML, there is a field "PHONE_DECIMAL" instead of...

[Soda supported data types for Snowflake](https://docs.soda.io/soda/connect-snowflake.html#supported-data-types) has the following table: Category | Data type -- | -- text | CHAR, VARCHAR, CHARACTER, STRING, TEXT number | NUMBER, INT, INTEGER, BIGINT,...

As per your advice, I edited the `snowflakeType` entries to change VARCHAR(16777216) to TEXT and DECIMAL(38,0) to NUMBER(38,0). This resolved the mismatches on the varchar columns, but we still have...