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
Folks, I got a snowflake database with a "public" schema (Yes, lowercase enforced "public").
If I use this connection string: snowflake://user:password@account/MYDB/public It just says I'm unauthorized (schema doesn't exist)
If I use this connection string snowflake://user:password@account/MYDB/"public" it authorizes all right, but then there's an unexplained syntax error down the line:
dbdoc/schema.svg
syntax error in line 1 near 'public'
I've tried "'public'"'"public"' and "\"public\"" but none work.
I believe it might have to do with snowflake assuming any unescaped identifier is uppercase (therefore the authorization error) but the escaping messes with the SQL for exploring the schema.
Is there a combination of escaping that will work?
The text was updated successfully, but these errors were encountered:
@juli4nb4dillo
Sorry for the late reply.
Unfortunately, I don't have free access to Snowflake, so I don't have an immediate solution (that's why I'm calling it experimental).
Thanks @k1LoW , I ended up making a different schema without the lower-case restriction.
I'll be happy to contribute to the snowflake driver, though my experience with Go is very limited.
Folks, I got a snowflake database with a "public" schema (Yes, lowercase enforced "public").
snowflake://user:password@account/MYDB/public
It just says I'm unauthorized (schema doesn't exist)snowflake://user:password@account/MYDB/"public"
it authorizes all right, but then there's an unexplained syntax error down the line:I've tried
"'public'"
'"public"'
and"\"public\""
but none work.I believe it might have to do with snowflake assuming any unescaped identifier is uppercase (therefore the authorization error) but the escaping messes with the SQL for exploring the schema.
Is there a combination of escaping that will work?
The text was updated successfully, but these errors were encountered: