You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The write_pandas function does not behave as expected. When trying to write to a previous created table, the table name fails if the table was given in mixed case.
The table create works in mixed case, as do other queries, but the write_pandas() fails.
What did you expect to see?
Here's the runnable code.
this fails, with a "table does not exist error".
I expect to see consistent behaviour:
If we are not going to allow mixed case table names, we should error on creation and/or query, not only on the write_pandas call.
Can you set logging to DEBUG and collect the logs?
github-actionsbot
changed the title
Unexpected behaviour when using mixed case table names with write_pandas
SNOW-1943408: Unexpected behaviour when using mixed case table names with write_pandas
Feb 20, 2025
Thanks for raising the issue.
It seems this is an application usage issue. For any object in Snowflake if its in mixed case, you need to use quotes to preserve it else by default it will be in capital letter and thats why the 2nd scenario is working for you when you used all capital letters for the object name.
table_id = "TEMP_USER_IDS_"+ '123ABCD'
Also, you creating temporary table, these doesnt exist beyond session, so you have to use auto_create_table=True
Temporary table can't be existing table.
I am able to create the table and insert the data via the dataframe successfully in mixed table name.
Python version
Python 3.11.9 (main, Aug 14 2024, 04:17:21) [Clang 18.1.8 ]
Operating system and processor architecture
macOS-14.7.3-arm64-arm-64bit
Installed packages
What did you do?
The write_pandas function does not behave as expected. When trying to write to a previous created table, the table name fails if the table was given in mixed case.
The table create works in mixed case, as do other queries, but the write_pandas() fails.
What did you expect to see?
Here's the runnable code.
this fails, with a "table does not exist error".
If we use consistent cases, we are fine:
I expect to see consistent behaviour:
If we are not going to allow mixed case table names, we should error on creation and/or query, not only on the write_pandas call.
Can you set logging to DEBUG and collect the logs?
The text was updated successfully, but these errors were encountered: