My(SQL) Experience I have just wasted two hours of my life

[pyost 0]

Yes, it is really nice to use MySQL databases. If you use a CMS, like I do, it is also very easy. Just make a new database in CPanel and then run the CMS installation. But what if you want to make it more complicated? Just do what I did!I have decided to put another Joomla! CMS powered website on my hosting space. Since I didn't want to make it available right away, I dug out Xampp, which I tried using earlier, but didn't really like it. Now it was my only option, so I installed it. After make a new database, installing the CMS and adding some data, I found it prepared enough to be put online. That's where my troubles started.File upload went OK, and I somehow changed the configuration file so it could use the Xisto MySQL base I was about to upload. I started off with a simple phpMyAdmin gzipped database export. Even though I had everything in my head, how was I supposed to do it, there were still a few.. Drawbacks.. When I tried just simply restoring the database from the CPanel, but it just said "Restoring Database" and nothing else. Sometimes it also said "Creating Database", but I would get an empty database every time. When I switched to phpMyAdmin first I had troubles finding the improt function. Of course, it didn't work - it found a syntax error! The next thing I tried was using the query window (which I had troubles finding ). It also told me that I had a syntax error at a certain line. In order to purge the problem, I made an Xisto database export to compare these two. It was almost the same, except one thing. In some places, the localhost had COLLATE something blah blah latin_something (not sure what it said). When I tried removing that part and then starting a part of the code taken from the DB in the query window, it worked! After that I removed all the part containing the COLLATE command and queried the code. Luckily, it was the end of my problems! Now everything is working just fine.As far as I am informed, this problem has appeared because of different version of phpMyAdmin and/or MySQL (forgive me if I have made a stupid statement). So, is there a way to solve this problem without messing with the exported MySQL code? Just to know if I try something like this again..