RE: mysql - OT

Jared,  

    It's taken them how long to agree to stored procedures? And how long before they agree to look into native ACID compliance?? And how much longer to agree that Point In Time recovery is important? The point is that their fixated on query speed over everything else. PostGreSql on the other hand is seriously into providing features & functions that are part and parcel of Oracle and DB2. Basically since they've already got the part that MySql is playing catching up on.  

    Oh, and BTW since that's what part of this thread is all about: Most employers don't pay us the big bucks for the everyday fun of keeping a database up & running. Most decent sysadmins can do the same. What they pay you for is making sure a recovery situation doesn't occur and if it does to get the db back on line ASAP, like Yesterday. That's why they pay out the big bucks, to those who can stand recovering a db with the CIO & CEO looking over your shoulder while breathing fire down your back. BTDT.

From: Jared Still [mailto:jkstill_at_gmail.com] Sent: Monday, April 11, 2005 11:14 AM
To: Goulet, Dick
Cc: RMohan_at_arbinet.com; ORACLE-L_at_freelists.org Subject: Re: mysql - OT

On 4/11/05, Goulet, Dick <DGoulet_at_vicr.com> wrote:

        I agree, PostGreSql is much superior to MySql. So I'd propose changing

        out LAMP (Linus, Apache, MySql, PHP) for LAPP(Linus, Apache, PostGreSql,

        PHP). Makes a lot more sense as it'll take MySql at least another

        decade to catch up.=20         

A decade? Sorry Dick, I don't think so.

They are moving fairly quickly on development, with fair amount of funding
and support.

--

Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist

--

http://www.freelists.org/webpage/oracle-l Received on Mon Apr 11 2005 - 12:13:01 CDT