Well, I've been a die-hard mysql fan for two years now and have been using
it with php for a web-based app. It has never crashed on me and has
performed perfectly.
As our app has grown, we have found a need for subselects and complex
queries and the work-arounds were ok until our databases started getting
more data in them. Then the work-arounds SLOWED down real bad and looping
out of the code was no longer an option.
Yesterday I crossed over to Postgres. It broke my heart to do it, but I have
to say that it outperforms mysql hands-down on complex queries and the
subselects open new doors for us that we need to stay competitive. Porting
the app over to it is tedious but not difficult.
I'm going to miss the simplicity and ease of MySQL, but if you're doing an
app that's going to grow and need sophisticated stuff, you're going to need
Postgres.
I would also strongly suggest not storing your images in the database but
rather a link to the image.
I really didn't understand everything Postgres was capable of until I
started messing with it yesterday. Try it out...
Robert Dayton
Unconventional Solutions, Inc.
Creators of DForce
Internet Process Serving Software
88-30 Sutphin blvd
Jamaica, NY 11435
(718) 558-6081
(352) 343-0462
----- Original Message -----
From: "Chris Chabot" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Saturday, August 25, 2001 12:37 PM
Subject: MySQL Still a wise choice for developers?
> Dear Everyone,
> I have been looking at this mysql.com/org dispute for a while now,
> and i must say i am getting more and more wurried. I have been a
> faithfull user of MySql for some years now. Not because it is the 'best
> full features database out there', but because it serves my specific
> needs perfectly (easy intergration with PHP and support for tons of
> images stored in a database).
>
> First MySql was a commercial product, freely available for most
> situations, and all was well with me. Though i strongly prefer GPL, it
> was still a source tar.gz, and i can imagine a company needs to try to
> make money any way they can..
>
> Later MySql was GPL'd and i rejoiced.. No more wurries about finding
> out about licencing issues, and hoping for good 3rd party contributions
> to MySql.. All was well and my choice for MySql was only re-affirmed.
>
> Now, a few years after first using MySql, a major dispute seems to
> plague the 'image' of MySql, and posibly also the future of the product.
> Big disputes like this won't make any customer of mine choose my
> MySql-based product any faster, quite the oposite, and i have already
> recieved numorous questions from my clients about my MySql choice..
>
> I am not siding with any party, nor giving (or want to have) any
> opinion on this dispute, however it is hurting my buisness, and my faith
> in continued fast development in MySql. MySql is not 'there' yet, it has
> a while to go before it is 'there' (thats why external parties
> sponsoring or helping with mysql 4 sounded great). And any obstacles
> like this will make people doubt if it will 'get there'.
>
> For my clients, and my self, only the bottom line matters... will
> this still be a product of choice in a few years, and is it worth the
> investment of resources to use it.
>
> The last thing that wurries me is the lack of updates on the issue,
> when i, as a wurried client & customer go to the mysql.com website, the
> only thing i find is a 'open inventation for 2001/07/18'. Being
> deep-august i presume that has come and gone, and no results or
> communications can be found.. (and the changelog mentioning: All
> reference to Gemini DB removed). MySql.org offers even less information.
>
> So, my real question, is MySql still the top choice for developers?
> Can you affirm that my choice for MySql is the right one?
>
> -- Chris Chabot
>
>
>
>
> ---------------------------------------------------------------------
> Before posting, please check:
> http://www.mysql.com/manual.php (the manual)
> http://lists.mysql.com/ (the list archive)
>
> To request this thread, e-mail <[EMAIL PROTECTED]>
> To unsubscribe, e-mail
<[EMAIL PROTECTED]>
> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
>
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
