Lost Posts
This morning is not starting out particularly well. I logged into Gmail to discover that LISHost’s MySQL server has been having issues and that due to a MySQL table corruption issue three of my most recent posts have been eaten. Frustration doesn’t even begin to describe what I’m feeling. One of the posts was a fairly lengthly explanation of how to split your iTunes and iPhoto libraries if you’ve run out of space on your local hard drive. This I was able to recover from Rojo which apparently caches my feed. (YEAH!)
However, the other posts were ones which I’d save chronicling my wiki experiments and adventurers. Lots of good technical tidbits that I’ve been finalizing to put up. Because I hadn’t posted them yet, half of my chronicle is gone with no hope of recovery. I’m counting to a hundred right now, very slowly. Ironically, I’m not mad a LISHost or Blake. (Really I’m not.) Mostly, just I’m highly pissed at myself for not saving the thing as a Word document or something. It just goes to show how reliant I am on my blog to draft ideas, thoughts, and how tos. That being the case, because Blake warned me that things a little flaky still. I’ll be making my own backup when I finish rewriting and my wiki posts. That way if there is another snafu I’ll be prepared.
Can we all count this as another call to *please* use a real database (“real” in this case, meaning “One that actually guarantees data integrity”)???
Postgresql is lovely…