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
Let Plugins define Schema changes #4204
Labels
Milestone
Comments
sabl0r
pushed a commit
to sabl0r/piwik
that referenced
this issue
Sep 23, 2014
…account for longer strings ( fields config_os_version and config_device_type are not large enough ) Refs matomo-org#4204 Plugin schema example with DevicesDetection
sabl0r
pushed a commit
to sabl0r/piwik
that referenced
this issue
Sep 23, 2014
…account for longer strings ( fields config_os_version and config_device_type are not large enough ) Refs matomo-org#4204 Plugin schema example with DevicesDetection
sabl0r
pushed a commit
to sabl0r/piwik
that referenced
this issue
Sep 23, 2014
…er they were successfully installed + should fix the build (thx ArchiveCronTest)
sabl0r
pushed a commit
to sabl0r/piwik
that referenced
this issue
Sep 23, 2014
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Plugin developers can create new tables in the database, or alter existing tables to add fields.
In this process, it is common requirement to also maintain schema versioning for plugins. Piwik plugins have this built in.
The schema version is the same as the plugin version. When you release a new plugin version you can bundle with it some schema changes.
How to do this:
See an example of Plugin Schema Update in the DevicesDetection plugin here.
The text was updated successfully, but these errors were encountered: