On Aug 11, 2004, at 9:50 PM, Sam Tregar wrote:
How can I be so sure? I've worked with big complex systems running on both databases. I've watched Bricolage completely destroy user data despite using PostgreSQL's transaction support.
You did? Why was there never a bug report? I have not seen Bricolage lose data.
In contrast, Krang hasn't lost data yet, as far as I know. A few careful locks in the right places seem to be just what the doctor ordered for a moderatly complex content management system. And if the catastrophic happens, like a system crash, that's what nightly backups are for. Nightly backups might not be good enough for all applications, but they're good enough for a content-management system.
Well, I think I'll just let that comment stand for itself.
Experience. Wrestle with a database strewn with triggers, constraints, abstract types and functions sometime. You'll be begging to be back in the moderate mess of a badly designed MySQL DB. There's less there so there's just less to do badly. It may not be an emperical fact, but I didn't presented it as such!
But this is typical of the difference between a software developer and a DBA. I think that one of the main reasons that MySQL is so popular is that developers like it, because they don't have to think about DBA issues.
Hrm, I could say more, but we're pretty off-topic here. I'll hold my tongue now.
Cheers,
David
smime.p7s
Description: S/MIME cryptographic signature
