Here's a doozy of a bug: I changed my very first post's created_on date from 2003 (January) to 2002, in order to test out a plugin I was developing. Now that I've changed it back, though, MT still thinks this post is in 2002. It doesn't think so from specific information, but if I load posts from 2002 it will pick up on that entry, even though the created_on date has changed to 2003. (A search of 2003 gets all the posts just fine, though.)

I'm using Berkeley DB, not SQL, which could be important to the problem.

I've also noticed this affects other kinds of searches as well; the post that was moved to 2002, even though it was moved back to 2003, now screws up "first post" searches using start_val so that if you start on a date even as early as January 1, 2002, the first post found is the second post, not the first. (This is the kind of search used in MT::Util::get_entry().)

Is there some way to slap the database back into order so it forgets I ever moved the first post? [Oh, and there's a bonus problem: Is there a way to do this without changing the order of the entries? When I imported my posts from Blogger, the dates were reversed and so 350 is my first post, not 1. I've changed all the internal links to fit this order and it'd be a royal pain to change them to something else.]

Lummox JR