Project

General

Profile

Actions
Copy link

Refactor #28363

closed

get rid of title_and_lookup_key_length validation in NestedAncestryCommon

Added by Tomer Brisker about 5 years ago. Updated almost 5 years 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:
Red Hat JIRA:

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 1 (0 open — 1 closed)

Related to Foreman - Feature #27035: Drop support for MySQL for both development and production environmentsClosedLukas ZapletalActions
Actions
Copy link
 #1

Updated by Tomer Brisker about 5 years ago

  • Related to Feature #27035: Drop support for MySQL for both development and production environments added
Actions
Copy link
 #2

Updated by The Foreman Bot almost 5 years ago

  • Status changed from New to Ready For Testing
  • Assignee set to Shira Maximov
  • Pull request https://github.com/theforeman/foreman/pull/7506 added
Actions
Copy link
 #3

Updated by The Foreman Bot almost 5 years ago

  • Fixed in Releases 2.1.0 added
Actions
Copy link
 #4

Updated by Shira Maximov almost 5 years ago

  • Status changed from Ready For Testing to Closed
Actions
Copy link

Also available in: Atom PDF