Mercurial > hg
view hgext/infinitepush/schema.sql @ 42022:1f567a9e25bd
chistedit: change in-progress message
Saying "running histedit" is an artifact of when chistedit was a
separate thing from histedit. I found the message a bit confusing,
since wasn't I running histedit from the beginning, just from the
curses interface?
The whole thing is now histedit, both the curses interface and the
underlying procedure to apply a plan, so let's use a message that
doesn't make a distinction.
author | Jordi Gutiérrez Hermoso <jordigh@octave.org> |
---|---|
date | Tue, 26 Mar 2019 11:53:30 -0400 |
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;