[rt-users] RT 3.0.2 to 3.2.2 database migration

[Michael Smith]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


> -----Original Message-----
> From: rt-users-bounces at lists.bestpractical.com [mailto:rt-users-
> bounces at lists.bestpractical.com] On Behalf Of Mike.Frazer at ipay.com
> Sent: Friday, December 03, 2004 12:33 PM
> To: sheeri.kritzer at tufts.edu; Mike.Frazer at ipay.com
> Cc: rt-users at lists.bestpractical.com
> Subject: RE: [rt-users] RT 3.0.2 to 3.2.2 database migration
> 
> We aren't going about it in a standard way, really.  The "upgrade"
> is being
> done on a clean system.  The database is the only thing that isn't
> going to
> be completely fresh, as it will be backed up from the existing
> system and imported into MySQL on the new system.  I just want to
> make sure the import
> is going to bring everything over in the right manner.  From the
> way it sounds, I can still run the upgrade on the DB as long as I
> import it in its
> current layout before installation, right?
> 
> As for the MySQL 4.1 issues, I've seen things regarding the
> passwords in 4.1.  I don't know a whole lot about this, although
> documentation I've read
> for 3.2.2 have also mentioned this as being a problem.  I think it
> may have
> been the install notes that accompanied the installation, I really
> can't remember offhand.


http://dev.mysql.com/doc/mysql/en/Old_client.html

There's a new encryption method for passwords in 4.1.

Mike

-----BEGIN PGP SIGNATURE-----
Version: PGP 8.1

iQA/AwUBQbEMIpzgx7Y34AxGEQIWlgCdHeWVa/jVV/lpUIN+TLzh9mTg7LwAoL2q
YDYQxyp/oIJa1NFt56LxBYRx
=CT0v
-----END PGP SIGNATURE-----