-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Mark,
You are correct - the hard part is upgrading the database. Moving forward, we will provide a script to upgrade the database from one release to the next, but since we didn't have an official release out, we didn't have a starting point for creating that. What I have typically done to update the database is to use phpMyAdmin's feature of exporting the schema (select the database, then click Export; select SQL, check Structure, but do not check Data). Then, compare the exported schema with the vcl.sql file. If that proves to be too confusing, I can probably create an sql file for you that would bring your schema up to date if you can send me the exported schema of what you currently have. Josh On Wednesday January 20, 2010, Mark Gardner wrote: > Are there any hints on the best way to migrate from a release candidate to > 2.1? (I believe I am running vcl-2.1.r835953.) > > It seems that the most important problem is migrating the database. The > management and web code should be swapped out pretty easily. > > Mark - -- - ------------------------------- Josh Thompson Systems Programmer Advanced Computing | VCL Developer North Carolina State University josh_thomp...@ncsu.edu 919-515-5323 my GPG/PGP key can be found at pgp.mit.edu -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFLWhU1V/LQcNdtPQMRAu3oAJsGW7A9cmvFV/zrOonsxmSm/MelVQCdEYs6 fEkWdhXtzZu0cHDP2uMzj6E= =ta7g -----END PGP SIGNATURE-----