Description: ------------ I want to be able to manage my database between versions using MDB2_Schema. The following scenario: 1) Version 1.0.0 is deployed and used for a week 2) Added a couple of features, added a field to the database and upgraded to 1.1.0 which is used for an entire day before I find a serious bug. 3) Now I have to revert to 1.0.0 while the bug is fixed, but a lot of data has been saved in the db - also in the new field. I want to keep those changes, as they should be available again when I upgrade to 1.1.1 (the bugfixed 1.1.0). All this should be achieved using the PEAR installer, so I need to know how to put the database definitions belonging to each version (so the next installer will know that). And it would be nice with some kind of safe way to upgrade and downgrade between versions. An automatic way to do this with MDB2_Schema would be nice?

This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better. with the recent INSERT...SELECT addition it is now possible to save data before a table/field is lost and recover it back later.