Closed bastienboutonnet closed 1 year ago
To clean up and re-prioritize bugs and feature requests we are closing all issues older than 6 months as of Apr 1, 2023. If there are any issues or feature requests that you would like us to address, please re-create them. For urgent issues, opening a support case with this link Snowflake Community is the fastest way to get a response
I am curious as to why
get_columns()
implements using a select query from the info schema (https://github.com/snowflakedb/snowflake-sqlalchemy/blob/e1141b8ddfbc499d1b813ae1b791a0559312e6cb/snowdialect.py#L403) whiledescribe table
would get us the same kind of info.I see that at some point in the past your implementation was using
describe
(https://github.com/snowflakedb/snowflake-sqlalchemy/pull/33/files#diff-8a3053a35fc794b288420f7343bfbc575c18bc834c223c2aae201e0adcfdd5c0R455) so I am curious what is the reason why this was changed.It seems like this issue also talks about a related topic: https://github.com/snowflakedb/snowflake-sqlalchemy/issues/204 but there doesn't seem to be any resolution or conclusion on it.
I am asking because I personally would like to use
describe
instead and therefore re-implementget_columns()
but I'd rather check with you if I am missing something and the reason why you resort to an ultimately less performant implementation.**The questions below are irrelevant for this issue***
Please answer these questions before submitting your issue. Thanks!
What version of Python are you using (
python --version
)?What operating system and processor architecture are you using (
python -c 'import platform; print(platform.platform())'
)?What are the component versions in the environment (
pip list
)?What did you do? If possible, provide a recipe for reproducing the error. A complete runnable program is good.
What did you expect to see?
What did you see instead?
Can you set logging to DEBUG and collect the logs?