The Back End
In the interests of greater efficiency and data integrity, I converted to a MySQL backend from the default Berkeley DB.
If you want to try that, and have implemented ThreadedComments, be sure to modify the database schema before running mt-db2sql.cgi
(i.e., don’t make the same mistake I did).
You need to add two columns and an index to the database:
--- schemas/mysql.dump.orig Thu Mar 6 12:45:41 2003 +++ schemas/mysql.dump Thu Mar 6 12:48:05 2003 @@ -80,12 +80,15 @@ comment_email varchar(75), comment_url varchar(255), comment_text text, + comment_subject text, + comment_parent_id integer, comment_created_on datetime not null, comment_modified_on timestamp not null, comment_created_by integer, comment_modified_by integer, index (comment_created_on), index (comment_entry_id), + index (comment_parent_id), index (comment_blog_id) );
Anybody know how stable MySQL 3.23.55 is under MacOSX? Will I need to check periodically to see if the daemon has died?
Update: A couple of things did break.
<$MTEntryBody smarty_pants="2" process_tags="1"$>
worked before the upgrade, but caused rebuilds to fail after upgrading. Re-ordering it to<$MTEntryBody process_tags="1" smarty_pants="2"$>
fixed the problem (you can imagine how long it took to figure this one out!).- The mt-rssfeed plugin now requires an explicit choice of directory where the RSS feeds are cached. It defaulted to the
db
directory when using Berkeley DB. But now, with no path specified, rebuilds would “work,” but no RSS feeds would appear.
Re: The Back End
Just a comment (mainly to test whether the “Remember Me” cookie really is persistent now).
The MySQL database seems to be rock-solid. Makes me think about other things I could do with it…