Mercurial > hg
view hgext/infinitepush/schema.sql @ 46004:49b4ab1d9f5e
share: show warning if share is outdated while source supports share-safe
Previous patches in the series and some which are already committed implements
share safe functionality where config and requirements will be shared too.
Rolling this feature has a problem that existing shares may never upgrade as
they will never learn about the new config. To help the transition, we show a
warning message if the share source supports share-safe mechanism. This provides
the source repo ability to upgrade and pass on the message to shares that you
should reshare and upgrade too.
Differential Revision: https://phab.mercurial-scm.org/D9369
author | Pulkit Goyal <pulkit@yandex-team.ru> |
---|---|
date | Mon, 23 Nov 2020 14:15:26 +0530 |
parents | 03ff17a4bf53 |
children |
line wrap: on
line source
CREATE TABLE `bookmarkstonode` ( `node` varbinary(64) NOT NULL, `bookmark` varbinary(512) NOT NULL, `reponame` varbinary(255) NOT NULL, PRIMARY KEY (`reponame`,`bookmark`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8; CREATE TABLE `bundles` ( `bundle` varbinary(512) NOT NULL, `reponame` varbinary(255) NOT NULL, PRIMARY KEY (`bundle`,`reponame`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8; CREATE TABLE `nodestobundle` ( `node` varbinary(64) NOT NULL, `bundle` varbinary(512) NOT NULL, `reponame` varbinary(255) NOT NULL, PRIMARY KEY (`node`,`reponame`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8; CREATE TABLE `nodesmetadata` ( `node` varbinary(64) NOT NULL, `message` mediumblob NOT NULL, `p1` varbinary(64) NOT NULL, `p2` varbinary(64) DEFAULT NULL, `author` varbinary(255) NOT NULL, `committer` varbinary(255) DEFAULT NULL, `author_date` bigint(20) NOT NULL, `committer_date` bigint(20) DEFAULT NULL, `reponame` varbinary(255) NOT NULL, `optional_json_metadata` mediumblob, PRIMARY KEY (`reponame`,`node`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8;