Welcome Guest ( Log In | Register )



 
Reply to this topicStart new topic
> My(SQL) Experience, I have just wasted two hours of my life
pyost
post Feb 28 2006, 04:56 PM
Post #1


Nenad Bozidarevic
Group Icon

Group: [MODERATOR]
Posts: 1,048
Joined: 7-November 05
From: Belgrade, Serbia
Member No.: 9,500
myCENTs:89.26



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 Astahost 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 biggrin.gif). It also told me that I had a syntax error at a certain line. In order to purge the problem, I made an Astahost 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..
Go to the top of the page
 
+Quote Post

Reply to this topicStart new topic

Collapse

> Similar Topics

Topics Topics
  1. What Is The Best Brand Of Harddisk?(65)
  2. Half-life 2 Questions(12)
  3. Mozart Life(4)
  4. Halo 2 Vs Half-life 2(33)
  5. Half Life 2/Steam WTF?(11)
  6. Garry's Mod: Half Life 2 Modification(11)
  7. Are Viruses Considered As 'alive'(47)
  8. Life Without A Computer(59)
  9. Social Life Is A Subforum For Superficial Phonies(3)
  10. What's Life As A Programmer Like In Your Country?(26)
  11. Do Dreams Really Mean Anything?(25)
  12. Half-Life 2 Is Outstanding(17)
  13. PC Takes Ages To Boot(8)
  14. Life In USB Stick(13)
  15. Installation Gone Bad...(14)
  1. My So-called Life(1)
  2. Half Life Dedicated Server(1)
  3. Life After Death?(33)
  4. Half Life 2: Episode 2(1)
  5. The Witcher Review(1)
  6. How Many Hours You Play Game?(11)
  7. The Experiment (experience 112)(4)
  8. The Future For Artificial Life(3)
  9. Second Life Review(2)
  10. Lesson Of The Day(5)
  11. When Does Human Life Begin?(4)
  12. My Experience With The Zlob Trojan(1)
  13. When And What Is Your First Linux Experience?(4)


 



- Lo-Fi Version Time is now: 2nd December 2008 - 12:05 PM