Re: The MySQL/PHP pair

"Marshall Spight" <mspight_at_dnai.com> wrote in message news:luGgd.441011$mD.362527_at_attbi_s02...
> "Kenneth Downs" <firstinit.lastname_at_lastnameplusfam.net> wrote in message
news:6oqqlc.8nm.ln_at_mercury.downsfam.net...
> >
> > But you know, it seems that there is a large group of people out there
> > developing against MySQL with PHP.
>
> Sure. If you've got a little small scale app with 1-3 developers,
> only one way into or out of the data (via the app), this will
> work fine. It won't scale up from there, though.
>
>
> > The logic seems to be that you need a
> > barrier beyond which bad data cannot go, but when the app is deployed
> > through the web, then that barrier is the web layer. If no user can
> > possibly SQL in, then the overpowering lure of PHP/MySQL leads to the
> > conclusion that biz logic can just go into the PHP and you get pretty
fast
> > to the Look Ma, It Works! stage.
> >
> > I just wonder if we have been unfair to MySQL.
>
> As someone who has been working closely with MySQL for 3 yeras now,
> I am confident that the people who beat up on MySQL have been
> overly nice. MySQL in the enterprise is a disaster.

That's good enough for me -- I'll return to my original opinion of the product, rather than trust the testimonials that suggest otherwise. Thanks! --dawn

>
> Marshall
>
>
Received on Sat Oct 30 2004 - 16:35:33 CEST