Bèr Kessels wrote:
Op woensdag 22 februari 2006 18:49, schreef Neil Drumm:
-Error avoidance. Module install and updates will happily go ahead and try to do things which are access denied and then think they are done. We need to check for access before doing these. One for each combinataion of alter/create and mysql/postgres to get started.
- Duplication avoidance: we have no way to avoid folks from rerunning the upgrade if the previous one failed, other thens some words to "not run the upgrade twice"
After each update the schema version in the system table is updated as well. So if the update selection page is regenerated after a half-update it will be okay. Maybe not perfect, since the browser may cache the previous form values if you use the back button, but certainly improved in 4.7.
- split of JoeSchmoe stuff and real stuff (sorry :). Upgrading joeschmoe.com is easy. It was done rather well, even in PHPnuke. Upgrading Bryght or web-log.nl[1] is a biatch, if not plain impossble w/o a lot of custom code.
It didn't happen in 4.6 so we can go without it for 4.7. Its not really a huge issue until you get into shared tables, where the same table would be updated twice by two sites. -- Neil Drumm http://delocalizedham.com/