On Thu, 12 Aug 2004, Chisel Wright wrote:

> On Wed, Aug 11, 2004 at 06:56:08PM -0400, Sam Tregar wrote:
> > > Also it seems to be MySQL specific.  Did I read that wrong?
> > 
> > Nope, you got that right too.
> 
> Out of interest, why MySQL? I know that lack of Postgres support is one
> reason that we didn't consider Krang recently when looking for a content
> management system recently.

That's too bad.  I'm not sure why you'd care which database your
content-management system was running on.  In most cases you'll hardly
notice unless it breaks, and I'd warrant that MySQL is a heck of a lot
less likely to break than PostgreSQL!

> Were there technical reasons

MySQL is, in my opinion, the best free database.  It's definitely
better than PostgreSQL and I should know, I spent more than a year and
a half working with it on the Bricolage project.  Of course, how one
defines "better" is subjective.  Here are a few observations that come
to mind:

  - MySQL is more stable.  The developers of MySQL do an absolutely
    amazing job vetting new releases before they're declared stable.
    I encountered exactly one bug in MySQL while developing Krang.
    Just one!  I don't have enough fingers to count all the bugs I saw
    in PostgreSQL while working on Bricolage.

  - MySQL is faster and easier to optimize when it's running slow.
    Indexes just work 99% of the time, unlike PostgreSQL's lame VACUUM
    ANALYZE run-around.

  - MySQL is easier to master and harder to abuse.  The set of
    supported commands is much smaller than most databases.  That
    means it's harder to end up with a rat's nest of a database
    schema.  Harder, but of course not impossible!

Now, to be fair, PostgreSQL has a lot of features that aren't present
in MySQL.  I tend to think most of them aren't all they're cracked up
to be, but I understand that a reasonable person can disagree.

> or was it a "I have time to make it work well with on database"
> thing?

Sure, that too.  My constant refrain while I led the Krang's
development was "YAGNI" - You Ain't Gonna Need It.  We definitely
didn't need to support more than one DB, so we didn't.  If someone
wants to come along and add PostgreSQL support, I think that's fine.
I think it's about as likely as someone porting Bricolage to MySQL,
but people talk about that all the time too!

-sam


-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
Html-template-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/html-template-users

Reply via email to