phorge-phorge/resources/sql/patches/041.heraldrepetition.sql

CREATE TABLE {$NAMESPACE}_herald.herald_ruleapplied (
  ruleID int unsigned not null,
  phid varchar(64) binary not null,
  PRIMARY KEY(ruleID, phid)
) ENGINE=InnoDB;

ALTER TABLE {$NAMESPACE}_herald.herald_rule add repetitionPolicy int unsigned;
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 07:53:53 -07:00			`CREATE TABLE {$NAMESPACE}_herald.herald_ruleapplied (`
herald: add the ability to execute a rule the first time only Summary: - added a new config class for representing the kind of repetition a rule has (once, every time, first time only) - added an email action to herald rules for differential to allow someone to get an email but only the first one - changed the herald rule ui to allow a user to pick the amount of repetition Test Plan: created a test rule and ran it over and over Reviewed By: epriestley Reviewers: epriestley, tuomaspelkonen CC: aran, epriestley, gc3 Revert Plan: Tags: - begin PUBLIC platform impact section - Bugzilla: # - end platform impact - Differential Revision: 357 2011-05-27 15:52:26 -07:00			`ruleID int unsigned not null,`
			`phid varchar(64) binary not null,`
			`PRIMARY KEY(ruleID, phid)`
			`) ENGINE=InnoDB;`

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 07:53:53 -07:00			`ALTER TABLE {$NAMESPACE}_herald.herald_rule add repetitionPolicy int unsigned;`