Hai there,

I am not able to upload my local database to remote.
A clean remote install of XOOPS however runs perfectly.

When I compare the local (with filled tables) db with the remote (clean) one, I notice a column in the local db (in the structure of the db) called "Collation" which isn't on the remote db.

Can this explain my problem?

Locally I run the XSAS environment, remote I run on PHP 4.3, MySQL 4.0.15 and phpMyAdmin 2.5.6.

I would be very glad to have this solved, I have a complete site waiting...

Thanks in advance and greetings,
Ronaldus

Are you running a charset other than latin1? I have never run into the collation field or options before so maybe someone with xsas experience can explain. But I think it has more to do with your local charset options.

xoops itself isn't adding the field but must be MySQL doing it based on the local settings which differ at the new server.

I think you could safely drop the field. You might try an export/import on the local server and then remove collation on the backup db and then export that to the new server. You still might have issues with the charset option being inserted. You can remove the option from the export file with an editor.

You should also install the 2.6 version of phpmyadmin at both ends to be safer.

Thanks for taking your time to help me, DonXoop.

I changed nothing in the charset settings, MySQL must have done this.
I'll try to open the export file in an editor and see if I can find the collation thing.
Do you think I can delete it totally?

Anybody with XSAS experience with a suggestion?

Greetings,
Ronaldus

BTW: both sides use phpMyAdmin 2.5.6., so that can't be the difference?
Can't I delete a whole column in the database structure?

How should I import a db from remote? Maybe I do something wrong there.
Now I connect to remote, go to SQL tab, browse to my local .sql file, uncheck 'show this quey here again' and press start.

Well DonXoop, started experimenting and succeeded!!
All works fine now!!
I'm a happy person.

But still very strange. All I did was skip all the
"ENGINE=MyISAM DEFAULT CHARSET=utf8" part out of the description of the db structure and then the remote phpMyAdmin accepted.

That meant a lot of work, but it was worth it.

Thanks for your help and greetings,
Ronaldus