No Comments

March 09, 2005

This night I was working on my site trying to make it unicode compatible. But due to an error in a script I removed the contents of all comments ever posted in the journal. Probably I shouldn’t work that late ;) Anyway, I’m already working on the problem, trying to reconstruct the most recent ones using Google’s cache functionality.

I’m one of those guys creating backups whenever possible. And so I also created a backup of my whole database every two weeks, using CocoaMySQL’s import/export functionality. And as I wanted to restore the contents I just got a huge list of error messages — damn. Any ideas? Additionally I’ve also contacted my provider, asking if they probably have a recent backup of my database… Anyway, I hope that I will find a way to restore my respectively your comments as soon as possible. Best regards and good night, Wolfgang.

Update

After some hours of work I was able to restore most of the comments. However, the most recent ones seem to be lost — sorry Allan, DonRalf and Julian. By the way Allan, would you be so kind and repost your comment concerning to use quicksilver in order to control iTunes, as it seems to be a topic many people would be interested in? Sorry for the inconveniences.

6 comments

CocoaMySQL’s dump is a simple SQL dump file, with a load of statements. I guess you’d want to filter to only do the ’INSERT INTO ’ statements. When you have those, you can just paste them in the ’custom query’ box, and run that. If it produces any errors, let me know the contents of the line and the error message itself (either here or by email) and I’ll take a look if you want.

Marten Veldthuis

Thank you for the hint — after modifying the dump file it worked perfectly. Great. However, the most recent entries are still lost.

Wolfgang

for me navicat works much better than all other apps. when interesting: www.navicat.com

karsten

Navicat seems to be a really interesting tool. I think I will have a closer look at it. Thanks.

Wolfgang

Uhm your Rss Feed contain a failure. Perhaps because of the unicode update?! line 130, column 90: ‘utf8’ codec can’t decode bytes in position 8635-8636: invalid data (maybe a high-bit character?) … viele Gerüchte vor einer Apple-Gro?eranstaltung wie diesmal vor der …

Fabian Aggeler

Thank you Fabian for the hint. I’ve already replaced the respective character. -----

Wolfgang

Commenting is not available in this channel entry.