Project

General

Profile

Refactor #28363

get rid of title_and_lookup_key_length validation in NestedAncestryCommon

Added by Tomer Brisker about 1 year ago. Updated 11 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Shira Maximov
Category:
Parameters
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
https://github.com/theforeman/foreman/pull/7506
Fixed in Releases:
2.1.0
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

Related to Foreman - Feature #27035: Drop support for MySQL for both development and production environmentsClosed

Associated revisions

Revision edcb23e2 (diff)
Added by Shira Maximov 11 months ago

Fixes #28363 - Drop lookup key matcher length limit

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

Also available in: Atom PDF