Kunal Mehta 419610bcdb Enforce category/page/position uniqueness constraint in the database ... Move location to two separate columns in the database: linter_start and linter_end. This allows us to have the database enforce the uniqueness of those fields, instead of just relying upon the PHP code to do so, which could be bypassed since we have multiple servers and concurrent processes. Change-Id: I3e67ce1b7cb3c93866a388ec3248af4cff2a81e0		2016-11-30 18:55:19 -08:00
..
ApiQueryLintErrors.php	Enforce category/page/position uniqueness constraint in the database	2016-11-30 18:55:19 -08:00
ApiRecordLint.php	Enforce category/page/position uniqueness constraint in the database	2016-11-30 18:55:19 -08:00
CategoryManager.php	Hardcode category ids	2016-11-22 18:31:17 -08:00
Database.php	Enforce category/page/position uniqueness constraint in the database	2016-11-30 18:55:19 -08:00
Hooks.php	Delete linter rows when pages are deleted	2016-11-22 18:31:21 -08:00
LintError.php	Enforce category/page/position uniqueness constraint in the database	2016-11-30 18:55:19 -08:00
LintErrorsPager.php	Enforce category/page/position uniqueness constraint in the database	2016-11-30 18:55:19 -08:00
RecordLintJob.php	Enforce category/page/position uniqueness constraint in the database	2016-11-30 18:55:19 -08:00
SpecialLintErrors.php	SpecialLintErrors: Implement getSubpagesForPrefixSearch()	2016-11-22 18:31:21 -08:00