-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Piwik Sequence table does not auto-update after changing DB prefix #9533
Comments
|
Why do we have to change prefix in some cases? Just to keep all our databases consistent (e.g. when we import existing database to Piwik Cloud). Would be nice to have a command/script to do the job. If there are issues with the |
|
|
I got that, what I don't get is how you change the prefix and recreate records. Like how do you do that step by step? Just to understand it better... I presume you basically import the tables into a database and then do a rename on the table names and that's it? Anyway, still thinking 1) is best solution so doesn't really matter. We can simply save it without the prefix and also update existing records in the sequence table |
@tsteur yes, our sys-admins were not aware that something may break after changing tables prefix and updating config file. Now the procedure is to update also records in the |
OK got it. We should remove it, maybe better for Piwik 3.0 to not break anything. If something goes wrong, there could be serious problems |
So the solution would be:
Assigning to LTS backlog. |
Steps to reproduce:
In this case, Piwik will create new records in
prefix_sequence
table and, unfortunately, will start with 0.There are two suggested solutions:
prefix_sequence
table.It's rather a critical issue. Currently the only way is to manually set the sequence records to max(idarchive) for each corresponding
archive_numeric
table.The text was updated successfully, but these errors were encountered: