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
There are 83 records on a view - currently I can only return 80 with a Select * from if I run a Select Count() from I get 83 records.
Within Snowflake if I run a sql query using the 2 statements above I can return 83 results.
If I run a select statement with the snowflake connector where I name specific columns named I can return 83 if I specifically exclude 2 date columns. If I include these 2 columns I return only 80 records.
Is this a security bug?
No, this is not a security bug
What is the severity of this bug?
Severity 1 - Connector is broken or there's a very serious issue
To Reproduce
There is no error presenting in the UI in Power Automate and the account has access to all the records.
Run sql queries where I increase the named columns returned and check the length of the array returned. Identify that the columns returned bring back 83 results. When the number of returned results drops to 80 check the column just added to the query statement and check data.
There is difference in the value returned on the columns - all 83 results show a date of 2099-12-31 00:00:00:000 but somehow this prevents all 83 results coming back.
No error presents and all 83 items be viewed with a sql query directly in snowflake.
I appreciate this is a weird error to reproduce - but we can do it on our instance.
Expected behavior
if I have 83 records in a view and I run a Select * from that view I expect to see 83 results or an error if there is a problem. The connector cannot be trusted if it does not return the expected results.
Environment summary
Install Method (e.g. pip, interactive script, apt-get, Docker, MSI, edge build)
CLI version (paconn --version)
OS version
Shell Type (e.g. bash, cmd.exe, Bash on Windows)
Additional context
i would love to see more documentation on the connector to allow debugging to try to assess why a sql query does not return all the expected values.
The text was updated successfully, but these errors were encountered:
Type of Connector
Certified Connector
Name of Connector
Snowflake Submit SQL Statement for Execution
Describe the bug
There are 83 records on a view - currently I can only return 80 with a Select * from if I run a Select Count() from I get 83 records.
Within Snowflake if I run a sql query using the 2 statements above I can return 83 results.
If I run a select statement with the snowflake connector where I name specific columns named I can return 83 if I specifically exclude 2 date columns. If I include these 2 columns I return only 80 records.
Is this a security bug?
No, this is not a security bug
What is the severity of this bug?
Severity 1 - Connector is broken or there's a very serious issue
To Reproduce
There is no error presenting in the UI in Power Automate and the account has access to all the records.
Run sql queries where I increase the named columns returned and check the length of the array returned. Identify that the columns returned bring back 83 results. When the number of returned results drops to 80 check the column just added to the query statement and check data.
There is difference in the value returned on the columns - all 83 results show a date of 2099-12-31 00:00:00:000 but somehow this prevents all 83 results coming back.
No error presents and all 83 items be viewed with a sql query directly in snowflake.
I appreciate this is a weird error to reproduce - but we can do it on our instance.
Expected behavior
if I have 83 records in a view and I run a Select * from that view I expect to see 83 results or an error if there is a problem. The connector cannot be trusted if it does not return the expected results.
Environment summary
Install Method (e.g. pip, interactive script, apt-get, Docker, MSI, edge build)
CLI version (paconn --version)
OS version
Shell Type (e.g. bash, cmd.exe, Bash on Windows)
Additional context
i would love to see more documentation on the connector to allow debugging to try to assess why a sql query does not return all the expected values.
The text was updated successfully, but these errors were encountered: