Inconsistent schema in precache_urls |
|||||
Issue descriptionPrecacheURLTable::CreateTableIfNonExistent() issues a CREATE TABLE for new users, and for old users, an ALTER TABLE to add various columns. The CREATE TABLE for is_precached does not specify a default value, but the ALTER TABLE specifies a default of 1. So we've got users with both schemas out there. I'm not sure what the impact of this is. We should evaluate the impact, figure out what the default should be, send a change to correct users' schemae, and figure out whether it's bad enough that we should cherry-pick.
,
Apr 11 2017
,
Apr 11 2017
,
Apr 12 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 12 2018
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by twif...@chromium.org
, Dec 21 2016