Skip to content

Removing MySQL 8.0 as default from local server#971

Closed
filter182 wants to merge 1 commit into
masterfrom
JC-PD-2185
Closed

Removing MySQL 8.0 as default from local server#971
filter182 wants to merge 1 commit into
masterfrom
JC-PD-2185

Conversation

@filter182

Copy link
Copy Markdown
Contributor

@wisyhambolu wisyhambolu left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A few comments need to be removed. We should avoid commenting out code as it creates noise within the codebase.

Also, 8.0 references need to be removed in https://github.com/humanmade/altis-local-server/blob/master/docs/database.md also which are missed from this PR.

// Suppress mysql_native_password deprecation warning
// Only affects in-place upgrades from MySQL 5.7 to 8.0.
'command' => $version === '8.0' ? '--log-error-suppression-list=MY-013360' : '',
//'command' => $version === '8.0' ? '--log-error-suppression-list=MY-013360' : '',

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should not be commented out but rather removed.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll close this PR as you mentioned in the ticket that this should be a separated PRs, doing this on that PR

Comment on lines 476 to 477
// Suppress mysql_native_password deprecation warning
// Only affects in-place upgrades from MySQL 5.7 to 8.0.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These need to be removed also as they a re 8.0 specific.

@mikelittle

Copy link
Copy Markdown
Contributor

@filter182 JC, One thing that is always useful is to connect a PR to the ticket it addresses via the Zenhub widget. You'll need the Zenhub browser extension or view the PR in Zenhub.
SCR-20260709-mpak

It makes a direct link to the PR from the Zenhub board.
Before:
SCR-20260709-mowa

After:
SCR-20260709-mpht

@filter182

Copy link
Copy Markdown
Contributor Author

@filter182 JC, One thing that is always useful is to connect a PR to the ticket it addresses via the Zenhub widget. You'll need the Zenhub browser extension or view the PR in Zenhub. SCR-20260709-mpak

It makes a direct link to the PR from the Zenhub board. Before: SCR-20260709-mowa

After: SCR-20260709-mpht

@mikelittle I think I did that but I was getting the message that I needed to re-auth that extension which it seems that it didn't work, also in other instances I have the issue that it doesn't allow me to liking because it simply doesn't show the ticket to be lined with

@filter182

Copy link
Copy Markdown
Contributor Author

closing this in favor of #985 and #986

@filter182 filter182 closed this Jul 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants