Hi,
I have just bought a nfo server and exported my old database via phpmyadmin from my old host and have imported it on my new one with nfo.
However, now I am getting this database error:
https://pastebin.com/rQRM2ATm
Does anyone know what exactly it means?
Everything works fine if I switch back to my old hosts database.
Database error
-
- New to forums
- Posts: 6
- https://www.youtube.com/channel/UC40BgXanDqOYoVCYFDSTfHA
- Joined: Thu Jun 08, 2017 7:32 pm
Re: Database error
It looks like your table ps2_HatPersistence was not copied over properly, from that.
When importing, you may need to turn off foreign key checks temporarily.
I also recommend against using InnoDB unless you really need it.
When importing, you may need to turn off foreign key checks temporarily.
I also recommend against using InnoDB unless you really need it.
Re: Database error
I am I using InnoDB? I was unaware of that. How would I change that?Edge100x wrote:It looks like your table ps2_HatPersistence was not copied over properly, from that.
When importing, you may need to turn off foreign key checks temporarily.
I also recommend against using InnoDB unless you really need it.
Re: Database error
I couldn't find the edit button. I did what you said and disabled foreign keys, but still same error =(
Re: Database error
Are you receiving an error when you do the import?
Re: Database error
Hi, no the addon throws me the error in the console when it's trying to do stuff in the database.Edge100x wrote:Are you receiving an error when you do the import?
It's not really something wrong the addon, but I have contacted the author anyway - to see if he knows what the issue could be.
Re: Database error
The problem must be with the mysql server or phpmyadmin that runs on the webserver. Since I uploaded the exact same exported file on my old database and it works.
Re: Database error
I solved the issue! =)
Apparently the script wanted to create new tables and that conflicted with current data. So I had to rename the old tables to the new one and import data one by one.
Apparently the script wanted to create new tables and that conflicted with current data. So I had to rename the old tables to the new one and import data one by one.