Bug #80763
closed
New hash version in ReferenceIndex can cause non-unique keys
100%
Description
The new hash version in ReferenceIndex ignores the sorting field. The updater in the install tool fails when the reference index currently has two distinct hashes for the same field which only differ in the sorting column. With the new hash calculation this will result in an identical hash, leading to unique constraint failures as the hash field is the primary key of the sys_refindex table.
These duplicate keys can be identified programmatically and should be cleaned up prior to modifying the hash values.
Updated by Gerrit Code Review about 7 years ago
- Status changed from Accepted to Under Review
Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/52398
Updated by Gerrit Code Review about 7 years ago
Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/52398
Updated by Gerrit Code Review almost 7 years ago
Patch set 3 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/52398
Updated by Morton Jonuschat almost 7 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset 193040353f086143a93eada81affb7bd8a8bdf73.
Updated by Xavier Perseguers almost 7 years ago
- Related to Bug #80347: sys_category_record_mm misses UNIQUE INDEX on combination of uid_local, uid_foreign, tablenames, fieldname added
Updated by