-
Notifications
You must be signed in to change notification settings - Fork 272
Diff found when comparing float columns between Postgresql & Snowflake #379
Comments
UPDATE: upgraded to the latest version (0.3.2), and I still get the same result. |
This issue has been marked as stale because it has been open for 60 days with no activity. If you would like the issue to remain open, please comment on the issue and it will be added to the triage queue. Otherwise, it will be closed in 7 days. |
Although we are closing this issue as stale, it's not gone forever. Issues can be reopened if there is renewed community interest. Just add a comment and it will be reopened for triage. |
Hi, I think this issue is still relevant... Would be glad if it could be fixed... |
Hi @yonieilon, I'm sorry for the delay in following up on this. Thank you for taking the time to raise this issue! We made a hard decision to sunset the data-diff package and won't provide further development or support. If that's of interest, over the past few months, we have rewritten the diffing engine in Datafold Cloud and solved many issues that existed in this package, including better handling of numerical comparison. -Gleb |
Describe the bug
When I compare a table between Postgresql & Snowflake, which has "double precision" columns in Postgresql and "FLOAT" columns in Snowflake, data-diff detects a diff, due to the way each db-engine rounds to the minimum precision, even though the actual value in the tables is equal.
Steps to reproduce:
The command or code you used
I can see it's running these statement in Postgres & Snowflake:
And indeed it's producing a different result in each db, since each DB engine rounds differently when casting to
decimal(38, 7)
Is there any workaround or way to configure data-diff to compare the value correctly???
Describe the environment
data-diff version: 0.3.1
The text was updated successfully, but these errors were encountered: