I have always been a belt and suspenders kind of guy so my tendency would be to lean to the safe side. I guess the thing is would a user ever want to go back. When I did it, I was not sure I would want to stay on the trunk as it was a bit of an unknown. But, in reality, it will likely be a one way affair for 99.5% of the users, so creating a new db is probably unneed overkill.
Tim On Sat, 2007-11-17 at 23:47 +0000, [EMAIL PROTECTED] wrote: > On 17 Nov 2007, at 20:14, Tim Madden wrote: > > > Here is the process that I followed to convert my 1.043 database to > > the 1.5 database. I am assuming that the user has already installed > > the new tracks on the system. (although maybe this should be > > included as well) > > > > > 3. Create new tracks 1.5 database > > > > Code: > > mysql -uroot -p > > mysql> CREATE DATABASE tracks15; > > mysql> GRANT ALL PRIVILEGES ON tracks15.* TO [EMAIL PROTECTED] \ > > IDENTIFIED BY 'password-goes-here' WITH GRANT OPTION; > > In the upgrade instructions I committed today [1], I went with making > a dump of the db as a backup, then just running rake db:migrate. I did > consider suggesting making a new db, but it's a bit more involved, and > for those running Tracks on a web host, they might be limited in the > number of dbs they can create. But creating a new db, importing a dump > of the old db and upgrading that is obviously less risky if something > goes wrong in the upgrade process. > > What do people think -- is it worth suggesting both methods as > alternatives in the docs? > > [1]: http://dev.rousette.org.uk/browser/trunk/tracks/doc/upgrading.html > > cheers, > > bsag >
_______________________________________________ Tracks-discuss mailing list [email protected] http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
