Go to Making Light's front page.
Forward to next post: Housekeeping notes from all over
Subscribe (via RSS) to this post's comment thread. (What does this mean? Here's a quick introduction.)
We are, and you may resume commenting whenever you wish. With the patient assistance of Steve Cook (check out his splendid weblog), we appear to have successfully ported all of Making Light and Electrolite from gunky old Berkeley DB to snazzy, fast-moving MySQL. Yes, just days ago we would have said “huh?” just like you’re doing now, but rest assured this will give us ever so many more tools for fighting evil and doing good. Right now we’re both going to have a stiff drink.
It’s possible some formatting oddities will turn up in the archives as a result of all this. Please feel free to let us know about them so we can fix them.
I sure appreciate that you (both)(and friends) do all this work so that I can read the interesting stuff and participate in the conversation. Thanks.
* poke *
* prod *
Yeah, seems to be working. W00t.
Wassail!
Another year or two, and it'll be postgresql. :)
Yay!
btw, the porn spammers are back. Why is it always about enlargement? Why can't it ever be about, say, rainbow colours? Or festive patterning?
(yes, I have insomnia.)
Well, I will throw an exception to describing BerkelyDB and MySQL is such terms. BerkleyDB is a simplistic format, true, but it has been beaten on for a long time, and stands well. (MySQL, in later versions, has become a true RDBMS, rather than a SQL interface to flat files, so we are now comparing Apples to Not-Apples.)
MySQL, however, is new, feature creeping, and my experiences with it are poor. But if you need it for the tools you need to run, you need it. (This is why, for example, I've gotten good at feeding MS-SQL databases. I'd rather not, but it pays.)
Dump those DBs early and often. If you don't know how, ask, and we'll tell you. But the recovery procedure for almost *all* RDBMS is simple -- drop the damaged tables/databases, restore from backup. You don't have a backup? Hmmm. Have a backup. Cron is just the thing. Ask if you need scripting help here.
Point in MySQL's favor. LiveJournal apparently runs on it. Point against. They're having real problems on a few of the DBs.
From the irony department: MySQL is highly configurable and gives the DBadmin a lot of control over tuning its back-end storage engine. A number of different low-level storage systems are available, depending on what you plan to use for RDBMS for ... and one of them is DBM, the most recent descendant of Berkeley DB.
).egap ym ta pu eraxip haraS eroM :sp( .enod llew boj a no enoyreve ot stargnoC .smelborp on -- em ot enif skooL
W piK
Um, the comment URL redirect thing is a clever idea, except it appears to be broken at the moment. Clicking on Kip W's name above (the URL is http://www.nielsenhayden.com/mt/mt-comments.cgi?__mode=red&id=37527) gives me:
Not Found The requested URL /mt/mt-comments.cgi was not found on this server. Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request. Apache/1.3.29 Server at www.nielsenhayden.com Port 80
However, manually changing the URL's mt-comment to qlbr yields haraS in all her Fierceness.
Works fine for me.
click here if not redirected and a distinct but not over long pause, and the page loads. Works for Charlie's page, too. (That's with Konqueror, a potentially useless data point for our hosts. :)
Whee!
MySQL roxors the hizouse!
*honourary streaking on the occasion of ML opening for comments again*
Looks like it's fixed now. Cool.
umm. Odd thing in my browser... In the Movie Reviews post all the apostrophes seem to have become the number 92. I use a fairly recent IE.
Same here. We'll clean it up in a few minutes. Thanks for the heads-up.
great to find you, and all of your upstanding linkage.
Namaste'
Thanks for the steer to Steve Cooks blog - some very nice writing there.
"However, manually changing the URL's mt-comment to qlbr yields haraS in all her Fierceness."
"qlbr" is of course a reference familiar to all attendees of Leo O'Flaherty's Latin class at Coronado High School, Scottsdale, Arizona, 1972-73, but "haraS in all her Fierceness" escapes me.
Nice work. This setup works better in Opera, as a fringe benefit.
Sorry to exceed your obscurity threshold, Patrick, though I did just experience a brief moment of unworthy pride at the idea that I had managed to stump you.
Herewith an explanation of "haraS in all her Fierceness":
W piK had said "egap ym ta pu era xip haraS eroM", and I was attempting to follow the link on his name to his egap, which has a xip of haraS captioned "Sarah ... looking Fierce" (and boy, she sure does!).
...What Erik said.
I dunno how Sleepycat's Perl interface works, but with PHP it's smooth as pudding.
For all that, IMO an SQL derivative is a better choice for high-traffic, MT-powered sites like the ones 'round these parts.
Another notice: ñ seems to turn into "f1", as seen in my comment in the Observation thread. Something to do with non-ascii characters, perhaps? ("F1" is the hexadecimal encoding/value for "ñ" in ISO 8859-1.)