Maybe I should replace my weblog with one that’s completely database driven. After all, databases never fail…
jtablesession::Store Failed
DB function failed with error number 1194
Table ‘jos_session’ is marked as crashed and should be repaired SQL=INSERT INTO `jos_session` ( `session_id`,`time`,`username`,`gid`,`guest`,`client_id` ) VALUES (‘0eb025f4839fcddf3a5af540c031c974’,‘1248672592’,‘’,‘0’,‘1’,‘0’ )
I don’t know about you, but static files seem like a much more cozy way to minimize the number of ways a hacker can come charging in and mess with your online journal. Of course it means that you won’t be hip and with it like all of the q00l A-list weblogs, but at least people might be able to see your commentary.
Comments
Lynn Dobbs
Mon Jul 27 07:50:01 2009
Comments are closed
That was not a database failure. That was a programming failure.
That said, unless one needs to mine the stored information in more than a straightforward text search way, flat files are a good thing. Easy to backup and restore, for instance. They are not inadvertently inaccessible because the newly installed database backup can’t read the old database format. And they don’t require any particular service to be running for access.
For a journal or diary running on one’s own server, flat files are probably a much simpler way to go.
That said, I like playing with the database so I tend to use it even when I know it is the wrong approach. ;)