Of course, this was in the days when dBase was the state of the art in PC databases, when SQL was something that only ran on IBM mainframes, and so a relational database would not have been possible even if I’d wanted one. My real point is that I know from personal experience that even WordPress could be mostly implemented without a relational database. Relational databases too often are being used because that’s what people get taught in college nowadays, not because they’re necessarily the right tool for a particular job. In a way I’m glad XML has come along, because it sounds just trendy enough that I can get away with avoiding the complexities of feeding a SQL database for most of what I do nowadays (which, granted, is not managing massive amounts of infinitely-searchable data).
MySQL is why my posts from the pre-2004 era aren’t online anymore. I got tired of fighting it and thus let it quietly die when I migrated to Blogger.
– Badtux the Geeky Penguin
]]>You really need to over-design data bases before you use them, or they will bite you hard.
People who are only users, have no idea how badly they can muck things up when they make changes. There are a lot of “plug-ins” available that permit you to do very dangerous things to the data base, especially if they aren’t constantly updated, because they do occasionally alter the data base when there is a software update. Fortunately the table names are descriptive enough that I checked before I got myself into deep yogurt.
There are a lot of very fast search algorithms that make flat files workable, avoiding the complexity of a data base. It’s not like you have to do a sequential read off a 9 track tape, like the old days.
Even this place has over 30K comments on 7K+ posts, so a flat file would be a problem.
]]>For extra fun, use one of the Open Source relational databases in a multi-threaded clustered environment, and watch the fireworks start :twisted:. I’m glad that’s not my job at my current employer…
– Badtux the Geeky Penguin
]]>The problem is the existence of what amounts to an indexing table that is automatically created for searching comments. If you change the main entry, you have to use SQL to patch the secondary indexing table or things seize up.
Fortunately I found a work-around before I mucked things up. It was a grim tale of disaster told by the guy who supplied the work-around, starting with his original belief that “back-ups are for sissies” and going down hill from there. He spent a weekend fixing things that were recoverable.
Apparently it was easy to do in early versions of WordPress, but as features were added simplicity was lost.
Data bases are wonderful things – until they crash.
]]>I moved it Steve, but I’m not going to do that again, because WordPress is really unhappy about that sort of thing and they really don’t want you doing it.
Next time I’m just going to put a link to the comment in the correct thread.
]]>I’ve been saying the exact same at my blog for years.
And no one is even budging from the gambler’s crouch.
Love ya,
S
]]>