Zed Pobre wrote: > The ideal way of handling this is to create SQL scripts that update > from one version to the next for each stage at which there was a > schema change, and for each database, and then make them available in > the schemas directory for users to run on their own. Potentially, the > could be run automatically based on the old version number during the > postinst, as well, if the scripts are idempotent (i.e. they would just > throw error messages if run on an already-updated database, rather > than corrupting the tables).
I'm planning to move the package to using the dbconfig-common framework sometime in the next month or two which should vastly improve this situation. The big blocker at the moment is that dbconfig-common does not yet support sqlite and I want to retain the ability for users to install phpwiki without the overhead of a "large" system like postgres/mysql. This is very definitely a release goal for PHPwiki's inclusion in etch however. -- Matt Brown [EMAIL PROTECTED] Mob +64 21 611 544 www.mattb.net.nz
signature.asc
Description: OpenPGP digital signature
