-
Notifications
You must be signed in to change notification settings - Fork 2
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
[COPA] Handle new case for log_no collisions #71
Comments
omar-carey-tw
added a commit
that referenced
this issue
Jan 29, 2020
omar-carey-tw
added a commit
that referenced
this issue
Jan 29, 2020
omar-carey-tw
added a commit
that referenced
this issue
Jan 29, 2020
khathuynh-tw
added a commit
that referenced
this issue
Jan 30, 2020
…ase schema; 4 tests in loader.py are flagged to be skipped
khathuynh-tw
added a commit
that referenced
this issue
Jan 30, 2020
khathuynh-tw
added a commit
that referenced
this issue
Jan 30, 2020
khathuynh-tw
added a commit
that referenced
this issue
Jan 30, 2020
omar-carey-tw
added a commit
that referenced
this issue
Jan 30, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The new case here is that it's possible to have a new row from the scraped COPA data like this:
log_no, beat, complaint_date
1234, 12, 2018-09-19
with a matching DB row that looks like this:
cr_id | beat_id | incident_date
1234 | None | None
final DB row should look like this:
cr_id | beat_id | incident_date
1234 | 12 | 2018-09-19
In this case the DB row should be updated to include the new information and a report describing this action created and saved under errors/updated_rows.csv
The text was updated successfully, but these errors were encountered: