Differential D18894 Diff 45308 resources/sql/autopatches/20180120.auth.02.passwordxaction.sql

Changeset View

Standalone View

resources/sql/autopatches/20180120.auth.02.passwordxaction.sql

This file was added.

				CREATE TABLE {$NAMESPACE}_auth.auth_passwordtransaction (
				id INT UNSIGNED NOT NULL AUTO_INCREMENT PRIMARY KEY,
				phid VARBINARY(64) NOT NULL,
				authorPHID VARBINARY(64) NOT NULL,
				objectPHID VARBINARY(64) NOT NULL,
				viewPolicy VARBINARY(64) NOT NULL,
				editPolicy VARBINARY(64) NOT NULL,
				commentPHID VARBINARY(64) DEFAULT NULL,
				commentVersion INT UNSIGNED NOT NULL,
				transactionType VARCHAR(32) COLLATE {$COLLATE_TEXT} NOT NULL,
				oldValue LONGTEXT COLLATE {$COLLATE_TEXT} NOT NULL,
				newValue LONGTEXT COLLATE {$COLLATE_TEXT} NOT NULL,
				contentSource LONGTEXT COLLATE {$COLLATE_TEXT} NOT NULL,
				amckinleyUnsubmitted Not Done Inline Actions So these are just booleans for tracking changes to `isRevoked`, right? amckinley: So these are just booleans for tracking changes to `isRevoked`, right?
				epriestleyAuthorUnsubmitted Not Done Inline Actions For now, yeah. The `Transactions` stuff serializes/deserializes these columns as JSON automatically, but the only possible values in this diff are "true" and "false". After D18897 we also write transactions when hashes are upgraded (e.g., from `iterated-md5` to `bcrypt`). I don't have any specific plans for other types of edits/transactions here, but we could now add them if they arise. Mostly, this is just a standard template table expected by the `Transactions` infrastructure. epriestley: For now, yeah. The `Transactions` stuff serializes/deserializes these columns as JSON…
				metadata LONGTEXT COLLATE {$COLLATE_TEXT} NOT NULL,
				dateCreated INT UNSIGNED NOT NULL,
				dateModified INT UNSIGNED NOT NULL,
				UNIQUE KEY `key_phid` (`phid`),
				KEY `key_object` (`objectPHID`)
				) ENGINE=InnoDB, COLLATE {$COLLATE_TEXT};