@mattab opened this issue on January 8th 2015

The goal of this issue is to ensure that in Piwik 2.11.0, Piwik 2.12.0, Piwik 2.13.0 and maybe Piwik 2.14.0 we do not introduce any major schema change impacting log_visit or log_link_visit_action.

In the meantime we will research a solution for the database to handle such schema changes in a more manageable way. Maybe Mariadb + TokuDB will solve this.

@mattab commented on February 8th 2015

See this comment which links to percona article: https://github.com/piwik/piwik/issues/6759#issuecomment-73435826

@mattab commented on April 22nd 2015

This issue still applies to 2.14.0 - but it is planned that in Piwik 3.0.0 we will be able to issue schema changes again (to be confirmed!)

@tsteur commented on June 9th 2015

Can we close this issue? I find it kinda useless and annoying seeing this all the time and it pollutes the milestone.

@mattab commented on June 9th 2015

@tsteur Moved to 2.15.0. We will be able to add schema changes in Piwik 3.0.0. I'd prefer to leave it opened while it's active to make this policy clear since it can be counter intuitive (eg. if new team members join)

@tsteur commented on June 9th 2015

I doubt they would directly make big changes to that and if so, we can still mention that if something potentially needs that ;) Also unlikely that someone would see it in the next milestone then

@mattab commented on July 30th 2015

Starting in 3.0.0 beta cycle, we can make database schema changes! :rocket: it feels good after 7 months to close this issue.

@mattab commented on September 27th 2016

There will be many schema changes in Piwik 3.0.0.

This issue was closed on July 30th 2015
Powered by GitHub Issue Mirror