Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Running piped SQL file that drops and adds a table produces different results on subsequent runs #467

Closed
timsehn opened this issue Mar 14, 2020 · 1 comment · Fixed by #471
Assignees

Comments

@timsehn
Copy link
Sponsor Contributor

timsehn commented Mar 14, 2020

Repo: corona-virus
Branch: case_details_virological_dot_org

This SQL: https://drive.google.com/open?id=1nZJyvSfZspMnIixZtmW3uRM0xYT7dloW

When run twice on the same working set produces no diff and the this diff summary:

Timothys-MacBook-Pro:corona-virus timsehn$ dolt diff --summary
diff --dolt a/case_details b/case_details
--- a/case_details @ ugcofv63pv8mqvq40h0esr4p7qm010qo
+++ b/case_details @ p11dee7ecl08h9g8ml3jrpnnqj48o5mm
48,601 Rows Unmodified (98.42%)                                         
0 Rows Added (0.00%)
779 Rows Deleted (1.58%)
0 Rows Modified (0.00%)
0 Cells Modified (0.00%)
(49,380 Entries vs 48,601 Entries)

It seems to deterministically delete all rows for the Hubei sheet source key with ID above 20463.

@zachmu
Copy link
Member

zachmu commented Mar 15, 2020

Reproduced this with latest build. Not sure what's happening yet, but have some ideas.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants