Module Upgrades and DB Schematics

[Mike Rockett]

So I've been wondering... What happens if a module gets an upgrade and it's DB table(s) need a schema update? Any decent way of handling this?

[netcarver]

@Mike

I don't think there is a "standard" way but the best I've seen so far is this, from one of Teppo's modules. You should be able to get the idea from the code.

[Mike Rockett]

That looks pretty decent indeed. Thanks

[kongondo]

@Mike,

Another example here from FieldtypeComments.

PS:

Please post all module related development stuff to the Module/Plugins sub-forum/board: Module/Plugin Development

https://processwire.com/talk/forum/19-moduleplugin-development/

This board is for 'Questions, answers and support for ProcessWire modules.' . Moving this thread there...

[Mike Rockett]

Ah, my bad... I'm quick to click!

Thanks

[bernhard]

thank you for this question mike, i was also wondering about this.

i did some research and found some links:

http://stackoverflow.com/questions/1607/mechanisms-for-tracking-db-schema-changes

http://dbv.vizuina.com/ especially http://dbv.vizuina.com/documentation/#usage-revisions-create

http://davedevelopment.co.uk/2008/04/14/how-to-simple-database-migrations-with-phing-and-dbdeploy.html

do you guys use any tools for tracking DB changes or do you create your change-scripts/dumps manually like in the example of dbv?