#include <twocents.h> The usual complaints regarding MySQL surface on large projects:
1) No transaction support (fixed with innodb, but up until recently a problem) 2) No sub-selects (which is a pain on a moderately complex system - makes for more awkward systems involving temporary table creation and joins) 3) No triggers/internal language ala pl/sql - again, this sucks for more complex systems, but is mostly work-round-able _iff_ you have full control over the code that talks to the database. The main body of code I work on, for instance, has a fairly complete OO layer overtop of the database code, so all interfacing with the database goes through a programmatic layer anyway, where trigger-like behaviour can be implemented. 4) incidental annoyances - lack of views, for instance. Having said that, it's faster than postgres in most situations, by all accounts (note: crass generalisation, I'm sure there's instances of the reverse too). Craig, I reckon calling MySQL a toy now innodb exists and is fairly stable is a bit harsh - given transactions, it's a capable database. It often still gets _used_ as a toy, but that's not it's fault. Triggers and pl/sql would be a nice add, but are not thoroughly necessary - and will, in fact, adversely affect your ability/likelyhood of writing a database-agnostic system (ie. you're more likely to lean on db-provided functionality, resulting in a system that's tied closely to one database instead of portable easily to MS/SQL or Oracle or whatever else). KJL (/me uses mysql and postgres, incidentally - more mysql than postgres, tho) On Sun, 2002-07-07 at 18:43, Theodor Milkov wrote: > > ----- Original Message ----- > From: "Craig Sanders" <[EMAIL PROTECTED]> > To: "Jeremy Zawodny" <[EMAIL PROTECTED]> > Cc: "Fraser Campbell" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> > Sent: Sunday, July 07, 2002 5:38 AM > Subject: Re: Admin for E-MAIL users only > > > > On Sat, Jul 06, 2002 at 07:34:31PM -0700, Jeremy Zawodny wrote: > > > On Sun, Jul 07, 2002 at 12:19:25PM +1000, Craig Sanders wrote: > > > > > > > > 1. use a decent database like postgres rather than a toy like mysql > > > > > > You're trolling, right? > > > > no. > > > > mysql is a toy. > > > > craig > > Not to feed the trolls, but I'm using mysql at our company since '99. > It have good performance and so far no serious problems. > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
