It's brilliant! Thank you! I'm sorry I didn't get a chance to try it earlier, I upgraded then never got around to testing it. The version upgrade was transparent, but instead of modifying the running database and installation I copied it to a new location, dumped the database, recreated it with a different name and then pointed the new install at the new database. Turned out not to be necessary, but I wanted to be able to roll back instantly in case there was a problem as the system is being heavily used by the schedulers. We have modifed about 10 files locally so sometimes the version upgrades break some of my patches. We are up to 300 events and 939 hours of programming, pentabarf seems to be handling it fine.
I'll make some local changes and release it for use after our schedule stabilizes in a few days. Aaron > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Sven Klemm > Sent: Thursday, February 23, 2006 3:13 PM > To: Pentabarf - Mailingliste > Subject: [pentabarf] Pentabarf 0.2.1 > > Hi, > > I tagged Pentabarf 0.2.1 in the repository. The only new > feature is the > visitor system, where people can login and create a personal schedule. > > The database of this version has changed compared to version 0.2.0. > There is a script called upgrade_0.2.0_to_0.2.1.sql in the > sql/maintenance directory. This script makes all necessary > modifications. Before executing this script you should of > course make a > backup of your database. > To upgrade from an existing 0.2.0 installation the following steps are > necessary: > - run upgrade_0.2.0_to_0.2.1.sql > - run views.sql in the sql directory > - run functions.sql in the sql directory > > Sven _______________________________________________ pentabarf mailing list pentabarf@mail.skyhub.de https://mail.skyhub.de/cgi-bin/mailman/listinfo/pentabarf
