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

Jump to bottom

Problem with already present PK in 3.6.0-b2.php #13805

Closed
fdellwing opened this issue Dec 5, 2018 · 1 comment
Closed

Problem with already present PK in 3.6.0-b2.php #13805

fdellwing opened this issue Dec 5, 2018 · 1 comment
Labels
answered For when a question was asked and we referred to forum or answered it.

Comments

@fdellwing
Copy link
Contributor

It seems that there are cases, there the addition of the new PK to site_setting breaks the updater.

Can you make sure to drop every possible present PK before adding the new PK?

refs: https://forum.matomo.org/t/aktualisierungsfehler-nach-update/30763

cc: @mattab @diosmosis
@tsteur
Copy link
Member

tsteur commented Dec 5, 2018

I've looked over all updates. In this case it looks like the user skipped an update (eg when executing SQLs manually or for some other reason). The table that was added in 3.0.0-b1 did not have a primary key. I don't think there's much to do here as it should be edge case. Haven't heard anything similar from another user, and if so, it should be easy to fix I suppose.

@tsteur tsteur closed this as completed Dec 5, 2018
@tsteur tsteur added the answered For when a question was asked and we referred to forum or answered it. label Dec 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
answered For when a question was asked and we referred to forum or answered it.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tsteur @fdellwing