>stores its weblogs in the MySQL database
Can you explain this to me? this seems like exactly what wordpress does..?
I think he meant "a log of accesses to the website" rather than "a blog." Those are often persisted on disk because they tend to get rather voluminous and the questions one wants to ask of them rarely benefit from SQL.
Re:Slashdot is Port Scanning Its Users
by davidgerard on Thursday April 10, 2014 @02:36AM
(#7564508)
I mean the Apache log!
Maybe it doesn't do that any more. BUT SOMEONE EVER THOUGHT THIS WAS A GOOD IDEA.
Re:Slashdot is Port Scanning Its Users
by NCommander on Wednesday April 09, 2014 @08:10PM
(#7563416)
backslash (the admin interface) is fragile, during beta testing, we got the site stuck in an infinite loop because the UI for topic creation is not the greatest. I'm not sure I get the 'stores weblogs in mysql' bit as wordpress by default does the same thing.
We've been discussing migrating over to PostgreSQL and rearchitecting the database to run on stored proceedures and views; almost all the DB calls are already abstracted in MySQL.pm, so this is relatively straight forward (if a bit tedious).
Really, Slashcode is just unbelievably horrible. I ran it myself. It's stupidly fragile, you can break it by altering things in the interface and it stores its weblogs in the MySQL database.
I eventually moved everything to WordPress and stopped wanting to STAB MYSELF IN THE FACE REPEATEDLY whenever I wanted to make a post.
Slashcode is not my favourite CMS.