Skip to content

Support for is_wip flag in DB #162

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

Closed
wants to merge 2 commits into from

Conversation

melange396
Copy link
Collaborator

No description provided.

…pdates.

Also fixed/improved setUp in integrations/server/test_covidcast_meta.py and added skeleton-code for new `missing_*` rows.
@melange396
Copy link
Collaborator Author

will we need to run this SQL in production, or does the database get truncated and repopulated?

ALTER TABLE `covidcast` ADD `is_wip` BINARY(1) DEFAULT (NULL);
UPDATE TABLE `covidcast` SET `is_wip` = 1 WHERE `is_wip` IS NULL and `signal` LIKE 'wip_%';
UPDATE TABLE `covidcast` SET `is_wip` = 0 WHERE `is_wip` IS NULL and `signal` NOT LIKE 'wip_%';

@krivard
Copy link
Contributor

krivard commented Jul 25, 2020

That SQL will probably be more efficient than trying to run the full data load again (iirc that had to run overnight last time)

@melange396
Copy link
Collaborator Author

i guess we can close this as the commits are included in #167 ?

@krivard krivard closed this Aug 4, 2020
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 this pull request may close these issues.

2 participants