Refactor #28363
get rid of title_and_lookup_key_length validation in NestedAncestryCommon
Pull request:
Fixed in Releases:
Found in Releases:
Description
This was introduced due to an issue with maximum length of mysql indexes. With MySQL support dropped, we can change the matcher field to text and drop this validation.
Related issues
Associated revisions
History
#1
Updated by Tomer Brisker about 1 year ago
- Related to Feature #27035: Drop support for MySQL for both development and production environments added
#2
Updated by The Foreman Bot 11 months ago
- Assignee set to Shira Maximov
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/7506 added
#3
Updated by The Foreman Bot 11 months ago
- Fixed in Releases 2.1.0 added
#4
Updated by Shira Maximov 11 months ago
- Status changed from Ready For Testing to Closed
Applied in changeset edcb23e247e06a5ac093ea56df8b748d1ef8a0e1.
Fixes #28363 - Drop lookup key matcher length limit