Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enrich log_visit table index by a third column #18636

Merged
merged 7 commits into from Jan 31, 2022
Merged

Enrich log_visit table index by a third column #18636

merged 7 commits into from Jan 31, 2022

Conversation

JasonMortonNZ
Copy link
Contributor

Description:

Issue: dev-2431

This PR improves the existing log_visit table index by including a third column within the index. The schema change will allow all new installations to benefit from the improved index, while the update script is earmarked for the 5.0.0 release.

Review

core/Updates/5.0.0-b1.php Outdated Show resolved Hide resolved
@JasonMortonNZ JasonMortonNZ marked this pull request as ready for review January 19, 2022 00:51
@JasonMortonNZ JasonMortonNZ added the Needs Review PRs that need a code review label Jan 19, 2022
Copy link
Member

@sgiehl sgiehl left a comment

Choose a reason for hiding this comment

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

@JasonMortonNZ This looks good now and should be good to merge
Just one last thing that needs to be clarified. How much of a need is the descending order? That is actually only supported by MySQL 8. Older MySQL versions will simply ignore the DESC

@tsteur If we are starting to use some MySQL 8 features, we maybe should recommend using MySQL 8 in our docs, even though we are still supporting older versions.

@tsteur
Copy link
Member

tsteur commented Jan 24, 2022

@sgiehl changed that guide to recommend MySQL 8.

Just one last thing that needs to be clarified. How much of a need is the descending order

It's not needed. On Cloud we don't run it on MySQL 8 either but it still helped.

@sgiehl
Copy link
Member

sgiehl commented Jan 25, 2022

@tsteur if that's the case, why do we know that a DESC key would be better, and shouldn't we then maybe change the other keys containing visit_last_action_time to DESC as well? 🤔

@tsteur
Copy link
Member

tsteur commented Jan 25, 2022

The find visitor query does a DESC and so the most others if I remember correctly. I don't think it's needed for the others but we could always test later down the road. We haven't seen any issues there so far.

Copy link
Member

@sgiehl sgiehl left a comment

Choose a reason for hiding this comment

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

Should be good to merge

@sgiehl
Copy link
Member

sgiehl commented Jan 31, 2022

@tsteur feel free to put this into a milestone it should be included or even merge it right away

@tsteur tsteur added this to the 4.8.0 milestone Jan 31, 2022
@tsteur tsteur merged commit ce27828 into 4.x-dev Jan 31, 2022
@tsteur tsteur deleted the dev-2431 branch January 31, 2022 19:43
peterhashair pushed a commit that referenced this pull request Feb 1, 2022
@peterhashair peterhashair mentioned this pull request Feb 1, 2022
3 tasks
@sgiehl sgiehl changed the title [Dev 2431] Enrich log_visit table index by a third column Enrich log_visit table index by a third column Feb 7, 2022
@sgiehl sgiehl mentioned this pull request Feb 7, 2022
11 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs Review PRs that need a code review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants