Project

Profile

Help

Task #5129

drop MariaDB support

Added by dkliban@redhat.com 3 months ago. Updated 27 days ago.

Status:
MODIFIED
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
Start date:
Due date:
% Done:

100%

Platform Release:
Blocks Release:
Backwards Incompatible:
No
Groomed:
Yes
Sprint Candidate:
No
Tags:
QA Contact:
Complexity:
Smash Test:
Verified:
No
Verification Required:
No
Sprint:
Sprint 59

Description

The reasoning for dropping MariaDB support was summarized on pulp-dev list0.

[0] https://www.redhat.com/archives/pulp-dev/2019-July/msg00035.html


Checklist


Related issues

Blocks Pulp - Task #5130: Remove maria/mysql from installer MODIFIED Actions

Associated revisions

Revision 75abd0fb View on GitHub
Added by dkliban@redhat.com 3 months ago

Problem: testing against mariadb is not needed

Solution: remove mariadb option from plugin-template

re: #5129
https://pulp.plan.io/issues/5129

Revision d3804e8f View on GitHub
Added by dkliban@redhat.com 3 months ago

Problem: mariadb no long supported by pulp

Solution: stop testing with MariaDB on Travis

This patch also brings in the latest changes from plugin_template. This includes
a template_config.yml in the root of the repository.

re: #5129
https://pulp.plan.io/issues/5129

Revision 68ac3216 View on GitHub
Added by daviddavis about 1 month ago

Drop reference to mysql/mariadb

ref #5129

History

#1 Updated by daviddavis 3 months ago

  • Groomed changed from No to Yes
  • Sprint set to Sprint 56

#2 Updated by amacdona@redhat.com 3 months ago

  • Blocks Task #5130: Remove maria/mysql from installer added

#3 Updated by dalley 3 months ago

In Pulpcore and Plugins, we should change CharField back to TextField where applicable. The only reason we used CharField was because MySQL cannot have an index on an unbounded text field.

In PostgreSQL this is not a limitation. There's no reason to use a 'varchar' type instead of a 'text' type unless you want a limit on the length of the text. They have identical performance (except for the overhead of the length check on 'varchar')

We should decide whether having a length limit on the field provides any value and remove it if not.

I don't see a compelling reason to switch back to autoincrement PKs despite the fact that we only moved away from them to begin with due to MySQL support.

#4 Updated by daviddavis 3 months ago

  • Checklist item add a blog post about why we're dropping support for mysql/mariadb added

It was also discussed that we should create a blog post for why we're dropping support. I think this is a good idea so I'm adding it to the checklist.

#5 Updated by dkliban@redhat.com 3 months ago

  • Checklist item update plugin_template set to Done
  • Checklist item update pulpcore travis config set to Done

#6 Updated by rchan 3 months ago

  • Sprint changed from Sprint 56 to Sprint 57

#7 Updated by rchan about 2 months ago

  • Sprint changed from Sprint 57 to Sprint 58

#8 Updated by daviddavis about 1 month ago

  • Sprint/Milestone changed from 3.0 to 71

#9 Updated by bmbouter about 1 month ago

  • Sprint/Milestone changed from 71 to 3.0

#10 Updated by rchan about 1 month ago

  • Sprint changed from Sprint 58 to Sprint 59

#11 Updated by daviddavis about 1 month ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to daviddavis

#12 Updated by daviddavis about 1 month ago

  • Checklist item update docs to state support of PostgreSQL only set to Done
  • Checklist item update pulpcore-plugin travis config set to Done
  • Checklist item update pulp_file travis config set to Done

#14 Updated by daviddavis 27 days ago

  • Status changed from POST to MODIFIED
  • % Done changed from 0 to 100

Please register to edit this issue

Also available in: Atom PDF