phorge-phorge/resources/sql/autopatches/20140325.push.2.eventphid.sql

ALTER TABLE {$NAMESPACE}_repository.repository_pushlog
  ADD pushEventPHID VARCHAR(64) NOT NULL COLLATE utf8_bin AFTER epoch;

ALTER TABLE {$NAMESPACE}_repository.repository_pushlog
  ADD KEY `key_event` (pushEventPHID);
Provide a real object ("PhabricatorRepositoryPushEvent") to represent an entire push transaction Summary: Ref T4677. Currently, we record individual actions in a push as PhabricatorRepositoryPushLogs, but tie them together only loosely with a `transactionKey`. Provide a real PushEvent object, and move some of the denormalized fields to it. This primarily just gives us more robust infrastructure for building, e.g., email about pushes, for T4677, since we can act on real PHIDs rather than passing awkward identifiers around. Test Plan: - Performed migration. - Looked at database for consistency. - Browsed/queried push logs. - Pushed a bunch of stuff. Reviewers: btrahan Reviewed By: btrahan Subscribers: epriestley Maniphest Tasks: T4677 Differential Revision: https://secure.phabricator.com/D8615 2014-03-26 03:43:26 +01:00			`ALTER TABLE {$NAMESPACE}_repository.repository_pushlog`
			`ADD pushEventPHID VARCHAR(64) NOT NULL COLLATE utf8_bin AFTER epoch;`

			`ALTER TABLE {$NAMESPACE}_repository.repository_pushlog`
			ADD KEY `key_event` (pushEventPHID);