Upgrading MySql and changing schema name. Upgrading MySql and changing schema name.
 

News:

cpg1.5.48 Security release - upgrade mandatory!
The Coppermine development team is releasing a security update for Coppermine in order to counter a recently discovered vulnerability. It is important that all users who run version cpg1.5.46 or older update to this latest version as soon as possible.
[more]

Main Menu

Upgrading MySql and changing schema name.

Started by jxmac18, January 03, 2005, 12:36:47 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

jxmac18

I'm wanting to complete an upgrade with the minimum downtime, so would appreciate any comments before completing this.  I've just upgraded Coppermine and PHP without much difficulty (although PHP 5 didn't play ball despite scouring through the forums).

Am running:
     Coppermine 1.3.2
     php            4.3.10
     MySQL        4.0.18
     MySQL Administrator 1.0.18

Am wanting to upgrade MySQL to 4.1.8.  I've searched the forum briefly, but are there any gotcha's anyone's come across that are specific to the Coppermine data stored in the database - columns no longer supported; changes to tables; changes to PHP; etc.

I've used "MySQL Administrator" to backup the database, and will just need to stop/remove the MySQL service first; load the new version; and restore the database.

Once MySQL is updated, I would like to change the schema name from "mysql" to something more relevant. The only place I can see in Coppermine is to change the "database" name in include/config.inc.php.


many thanks
Jack  ;D
We are the world; we are the tiny-insignificant-specks-of-sand-on-this-rock-called-home.

kegobeer

Upgrading MySQL should have no effect on Coppermine, as long as it's set up correctly.  It's like upgrading PHP, everything will work as long as you compile it with the minimum requirements Coppermine requires.

If you want to rename your Coppemine database and/or tables, go ahead.  Just edit config.inc.php to match your new names.
Do not send me a private message unless I ask for one.  Make your post public so everyone can benefit.

There are no stupid questions
But there are a LOT of inquisitive idiots

jxmac18

Worked pretty good. Msql 4.1 has some immediate improvements - the msi installer and MySQL Administrator work very well.

Had Mysql installed under c:\mysql and was able to install into c:\Program Files, and restored my data to a new schema.  It retained a "mysql" schema for what looks to be some internal functions.

After I'd updated the config.inc.php, found I couldn't connect to the database, but with "MySQL Administrator", I added:
- Service Control: Support for InnoDB
- Moved the database to a much faster RAID-5 array.
- Startup Variables: Security: Didn't have to specify "Use old passwords" - which I've seen mentioned on other posts.
- User Administration: Assign alll privileges to the root user for my new schema and the "mysql" schema (this seems to be the key reason for the database connection not working with Coppermine.

Certainly seems faster to access the photos.

Many thanks!
Jack
We are the world; we are the tiny-insignificant-specks-of-sand-on-this-rock-called-home.