Geeklog Forums

I have the database backup from geeklog 1.4.0sr5-1 but want to upgrade to 1.4.1. Can I do a new install of 1.4.1 with this backup from 1.4.0?

Also, no one ever answered this, but how do I split my db into parts? Godaddy has a 2mb limit per db file and my db is 5mb.

You can't do the new install of 1.4.1 and put the 1.4.0 data in there. Why don't you want to upgrade directly over 1.4.0?

If you want a clean install with old data, you can first upgrade the 1.4.0 site, and back up the data. Now the data is 1.4.1. Make new install, and replace the data from the back up.

Don't host with a webhost that does not provide you with enough space. There is thousands of webhost out there; you don't have to stick with Godaddy and bear the pain of the limitation.

Hope this helps!

Sam

I did the 1.4.0 to 1.4.1 upgrade and it screwed my database up. Now I have just the db backup file. I guess I need to install 1.4.0, add the backup, then upgrade but was hoping there might be an easier way since the upgrade updates the 1.4.0 db anyway.

Godaddy gives the space but only accepts the db in 2mb chunks. Some hosts do this.

You can cut a db after each table plus contents. Usually it starts like this with "create table" and then comes the contents with "insert into". If you keep these 2 components together, the creation of the table and its contents, then you can upload every table separately.

Thanks, I can use that in the future. Godaddy attempted to import the whole db but got this error, as explained by them:

"When attempting to import the database, we receive the error below. You will need to add the DROP IF EXISTS lines to your .sql file before we can import it.

Error at the line 17: ) TYPE=MyISAM;

Query: CREATE TABLE `gl_access` ( `acc_ft_id` mediumint(8) NOT NULL default '0', `acc_grp_id` mediumint(8) NOT NULL default '0', PRIMARY KEY (`acc_ft_id`,`acc_grp_id`) ) TYPE=MyISAM;

MySQL: Table 'gl_access' already exists

Stopped on error."

I did nothing to the db sql so Geeklog did this but why can't they import?

It can`t be imported because the db is already filled. You can either drop the tables in the db manually or write such a line "DROP TABLE IF EXISTS" in front of every "CREATE TABLE"

Do you understand the example? It is like the first two lines in the example above. The first line is necessary if the db is not empty.

Wait, so the schmucks didn't delete the old db before trying to import, is that it? That's what I get out of it. So either delete then import or add that line repeatedly?

Yes almost. You have a db and that got tables and there is contents in them. When reading back the "db" you actually only read back the tables and the contents.

Does godaddy have a phpMyAdmin? Can you import the db yourself? Then you could simple add that line DROP TABLE IF EXISTS `gl_access`; and so on and finally import it.

There also seems to be a problem with "Error at the line 17: ) TYPE=MyISAM;" I could imagine that the MySQL versions were different when saving and reimporting. Can you confim that? What is that line 17?

Lines 11-19 are:

CREATE TABLE `gl_access` (
`acc_ft_id` mediumint(8) NOT NULL default '0',
`acc_grp_id` mediumint(8) NOT NULL default '0',
PRIMARY KEY (`acc_ft_id`,`acc_grp_id`)
) TYPE=MyISAM;

--
-- Dumping data for table `gl_access`
--


Godaddy has phpMyAdmin but limits manual imports to 2mb. I opened the db wih CrimsonEditor and it says that part of it has over 32769 words and some date mit be lost if saved.

O.k. within phpmyadmin you can drop the tables manually.

You can simply split up the file to be imported by saving it in 2 or 3 pieces. You simply have to keep that pair of "CREATE TABLE" and the matching "INSERT INTO" together. Depending on the plugins you may have some 20-40 tables. Just save the first 15 or so as part1.sql and so on.

You can also .zip that .sql file, though there may be extra problems when uploading.

Thanks. What about the MyISAM error?

I'll try to use the current db first before importing since godaddy seems inept.

How did you save the db? Through GL, on the same system / webspace? Can you try to save the current db within phpmyadmin? Compare that line with TYPE=MyISAM;

Oh crap. It does look like the db version is 4.0 and godaddy now defaults to 4.1 with an option for 5.0. How big of an impact is this? Saved the db through GL and downloaded it with WS_FTP. Bad news though. Godaddy has it's own admin page; not sure if it's PHPmyAdmin. I see no import options, just export. I rather not setup phpmyadmin myself so I'm stuck with them. I did find some options that may help the export. Structure: Add DROP TABLE Add IF NOT EXISTS Export type: insert update replace I checked off both Add DROP TABLE and Add IF NOT EXISTS and a replace export. Okay, it added the DROP TABLE IF EXISTS. MyISAM looks the same. Here's the new code: DROP TABLE IF EXISTS `gl_access`; CREATE TABLE IF NOT EXISTS `gl_access` ( `acc_ft_id` mediumint(8) NOT NULL default '0', `acc_grp_id` mediumint(8) NOT NULL default '0', PRIMARY KEY (`acc_ft_id`,`acc_grp_id`) ) TYPE=MyISAM; I don't see how it differs.

This TYPE=MyISAM; can be a problem when the MySQLs are of a different version. If is it not different then give it a try. It is always better to save everything or even have a testing webspace.

Okay, godaddy uploaded it.

One other question. How can I split tables? My gl_stories is 3.1mb. I can manually import tables.

*sigh* I just did the upgrade but it's stuck. The msg says:

"Database already up to date!

It looks like your database is already up to date. You probably ran the upgrade before. If you need to run the upgrade again, please re-install your database backup first!"

I installed 1.4.1 yesterday with a new database. Godaddy overwrote the db with my 1.4.0 db. Then I hit upgrade to get that error.

Let's go over the steps. Which do I do first to upgrade?

I use GoDaddy as well and I just upgraded one of my geeklog sites from db version 4.0 to db version 5.0 and have had no issues what-so-ever. So I imagine you should not have any issues. I chose version 5.0 of mysql because of some of the new features I might use to further customize my geeklog sites. (ie: stored procedures and triggers)





This is how I did my upgrade, and it worked perfectly. First I backed up my old 1.4.0 geeklog database. Then I created a brand new empty database in GoDaddy. After creating the new database, I went into the new database through goDaddy's phpMyAdmin and restored my backed up 1.4.0 geeklog database. After restoring the old database I uploaded the geeklog 1.4.1 files and used the upgrade option. It worked perfectly.

I did not delete my old 1.4.0 database from goDaddy until I was certain everything went okay. I also, downloaded my 1.4.0 website onto my local machine before uploading 1.4.1 just in case something went wrong I could simply re-upload my old website and be back up and running again.