Closed jeffersonatsafe closed 1 year ago
Any chance https://github.com/snowflakedb/snowflake-jdbc/pull/418#discussion_r552139224 is relevant to this issue?
To clean up and re-prioritize more pressing bugs and feature requests we are closing all issues older than 6 months as of March 1, 2023. If there are any issues or feature requests that you would like us to address, please create them according to the new templates we have created. For urgent issues, opening a support case with this link Snowflake Community is the fastest way to get a response.
We believe this was actually fixed in https://github.com/snowflakedb/snowflake-jdbc/commit/4f8309888280a072dd3f280e6c67833a4dde0f40 (as long as you don't use "stage paths" per https://docs.snowflake.com/en/user-guide/data-load-considerations-stage.html#organizing-data-by-path)
hello snowflake team
as you may know, in Snowflake, obscure table names are supported, as long as they're surrounded by double quotes. To access the internal stage of these tables, one can escape the stage names using either
$$
or'
, as answered in this thread: https://stackoverflow.com/questions/59059001/snowflake-how-to-refer-to-internal-stage-for-specified-table-with-special-charProblem is,
SnowflakeConnecitionV1.uploadStream()
would automatically append@
character if the stage name does not start with@
character. Therefore, attempts to escape the obscure stage names will fail.can we either disable this automatic behaviour, or provide a 'strict' stage name method that would bypass it?
this was found in
snowflake-jdbc-3.9.2
thanks!