Author Topic: Schema Change Policy (Read 1210 times)

outinsun · July 08, 2009, 07:41:44 am

In http://wiki.civicrm.org/confluence/display/CRMDOC/Ensuring+Schema+Integrity+on+Upgrades it states that "When a CiviCRM site is upgraded to a new version, there are frequently changes to the structure of the database". Is there any policy related to schema changes and minor/major versions? If/when schema changes are made, are the changes noted in release notes? Would be helpful to folks who need to write custom scripts that touch the underlying database for some reason.

Dave Greenberg · July 08, 2009, 11:07:06 am

Schema changes (and additions to tables which define "enums" - mostly option_group and option_value tables) are part of both minor (e.g 2.2.7) and major (e.g. 2.2.0) releases. These changes are not (yet) documented nicely in set of release notes (the bad news). The good news is that we introduced an "incremental" structure for upgrades in 2.2 which provides pretty decent in-code documentation of the changes for each release.

Check out /CRM/Upgrade/Incremental/sql/2.2.1.mysql.tpl - and the other files in that directory to see the pattern. Each .mysql.tpl contains the DB modifications for that release.

CiviCRM Community Forums (archive)

News:

Author Topic: Schema Change Policy (Read 1210 times)

outinsun

Schema Change Policy

Dave Greenberg

Re: Schema Change Policy