phorge-phorge/resources/sql/autopatches/20140325.push.2.eventphid.sql at 0a83f253ed03829826a2e69e891358e80a3c3ba7 - revi-archive/phorge-phorge - SiliconForest Atelier

revi-archive/phorge-phorge

mirror of https://we.phorge.it/source/phorge.git synced 2024-11-10 08:52:39 +01:00

epriestley a5f55d506f 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 13:51:06 -07:00

5 lines

221 B

SQL

Raw Blame History

 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);