Mercurial > hg
view hgext/infinitepush/schema.sql @ 46100:a771ffc378a8
simplemerge: write output only once it's complete
`simplemerge()` can write either to `ui.fout` or to the file context
(for in-memory merge). This patch simplifies the code a bit by making
it build the output the same way regardless of where it's written, and
then writes the whole output at once. I don't think it will be a
problem that we don't output anything until the whole file is merged
even if the file is large.
Differential Revision: https://phab.mercurial-scm.org/D9550
author | Martin von Zweigbergk <martinvonz@google.com> |
---|---|
date | Wed, 09 Dec 2020 00:00:19 -0800 |
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;