phorge-phorge/resources/sql/patches/011.badcommit.sql

CREATE TABLE {$NAMESPACE}_repository.repository_badcommit (
  fullCommitName varchar(255) binary not null primary key,
  description longblob not null
);
SQL Patch Management: SQL Changes Summary: Splits out the SQL changes. These are most of the changes, but primarily mechanical: - Moved "initialize.sql" to "0000.legacy.sql" and partially reverted to an older version, such that patches 0000 + 000 + 001 + ... + 137 put us in the right state when applied sequentially. - Removed "create database" commands from all SQL. These are handled by separate DB patches now, so we have the data to do operations like "storage databases" (list databases) and "storage destroy" (drop databases). - Removed "phabricator_" namespace from all SQL, and replaced with "{$NAMESPACE}_" token so we can namespace databases. - Shortened some column lengths so patches apply correctly if originally created as InnoDB; also a few similar tweaks elsewhere. Test Plan: See D2323 for discussion and test plan. Reviewers: edward, vrana, btrahan, jungejason Reviewed By: btrahan CC: aran Maniphest Tasks: T140, T345 Differential Revision: https://secure.phabricator.com/D2329 2012-04-30 16:53:53 +02:00			`CREATE TABLE {$NAMESPACE}_repository.repository_badcommit (`
Derp derp, apparentl neglected to save this file. 2011-03-27 08:59:12 +02:00			`fullCommitName varchar(255) binary not null primary key,`
			`description longblob not null`
Allow commits to be marked as 'bad' so they won't be parsed. Useful if you work at a company where someone deleted the entire repository cough cough. 2011-03-27 08:52:09 +02:00			`);`