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

Remove update script for new profilable dimension #16244

Merged
merged 1 commit into from Jul 27, 2020
Merged

Conversation

tsteur
Copy link
Member

@tsteur tsteur commented Jul 27, 2020

refs https://github.com/matomo-org/matomo/pull/16217/files#r456216141
refs #16192

Thought it's better to remove this update as the value might be set wrongly in case someone updates from 3.14.0 to 4.0.0. Wanted to remove this in the PR directly but forgot to do it. Think it's better to have the dimension unset before setting it potentially wrongly. see https://github.com/matomo-org/matomo/pull/16217/files#r456216141

Was also thinking of changing it to "UPDATE $logVisit SET profilable = config_cookie WHERE profilable is null and visit_last_action_time < 2020-07-08" because nobody could have used 3.14.0 before first beta was released on 8th July but it would mean some visits have this dimension set while others don't and then it maybe becomes inconsistent. Could also add the date though.

refs https://github.com/matomo-org/matomo/pull/16217/files#r456216141
refs #16192

Thought it's better to remove this update as the value might be set wrongly in case someone updates from 3.14.0 to 4.0.0. Wanted to remove this in the PR directly but forgot to do it. Think it's better to have the dimension unset before setting it potentially wrongly.  see https://github.com/matomo-org/matomo/pull/16217/files#r456216141

Was also thinking of changing it to `"UPDATE $logVisit SET profilable = config_cookie WHERE profilable is null and visit_last_action_time < 2020-07-08"` because nobody could have used 3.14.0 before first beta was released on 8th July but it would mean some visits have this dimension set while others don't and then it maybe becomes inconsistent. Could also add the date though.
@tsteur tsteur added the not-in-changelog For issues or pull requests that should not be included in our release changelog on matomo.org. label Jul 27, 2020
@tsteur tsteur added this to the 4.0.0 milestone Jul 27, 2020
@sgiehl
Copy link
Member

sgiehl commented Jul 27, 2020

Guess completely removing it is better in this case. Using a date is inaccurate as well, as someone might wait a long time till updating to 4.0

@tsteur tsteur merged commit 2c584ec into 4.x-dev Jul 27, 2020
@tsteur tsteur deleted the profilable_no_update branch July 27, 2020 19:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
not-in-changelog For issues or pull requests that should not be included in our release changelog on matomo.org.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants