What’s gone is gone

Sunday, 21 September 2008

I had a look at my blog yesterday and to my horror, about 4 months of posts had disappeared. I agonized over whether I should go back over Google cache and repost lost articles, but in the end, I didn’t think it was worth the bother. After all, a blog is a notepad for ideas and framing one’s thoughts. Once written down, it’s purpose is served.

What would you have done?

Bookmark and Share

You should follow me on twitter here

The entry 'What’s gone is gone' was posted on September 21st, 2008 at 12:00 pm and last modified on September 22nd, 2008 at 1:30 pm, and is filed under General. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

4 Responses to “What’s gone is gone”

  1. Eric writes:
    No. 1 — September 24th, 2008 at 2:37 am

    I had wondered why a couple of your posts from 12 September were generating 404 errors by the time I noticed them in the Planet Python feed. Not a huge issue, but it is disappointing.

  2. Steve Holden writes:
    No. 2 — September 29th, 2008 at 11:45 pm

    Well, I was just about to quote your Cygwin SQLite post to someone on c.l.py, but I guess this means I can’t. However, I’d definitely be thinking about changing my hosting arrangements if that happened to me … now I’ll go search the Google cache.

  3. Chui writes:
    No. 3 — September 30th, 2008 at 1:55 pm

    Surprisingly, the entry appears to be still in the wp_posts table. It’s set to “published” too, so there has to be a bad join somewhere.

  4. Chui writes:
    No. 4 — September 30th, 2008 at 2:21 pm

    Turned out to be broken indexes.

    SELECT wp_title from wp_posts where wp_title like ‘%sqlite%’
    worked since it’s a table scan, but

    select wp_title from wp_posts where ID=479
    returned 0 rows.

    Solution: Rebuild indexes.

    repair table wp_posts QUICK;

Leave a Reply

«
»