Poll: Is MySQL a good choice for a web app?

What kind of data storage?

  • MySQL

    Votes: 38 80.9%

  • Postgres

    Votes: 2 4.3%

  • SQLite

    Votes: 0 0.0%

  • Flat files, baby!

    Votes: 1 2.1%

  • Other (MS SQL, Oracle, etc.)

    Votes: 3 6.4%

  • None, I don't like data, it burnssssss

    Votes: 3 6.4%
  • Total voters
    47
Status
Not open for further replies.


I think you should be using lotus.

WTF!?!?? Of course you should be using MySQL. How does this require a poll?
 
micker said:
I think you should be using lotus.

WTF!?!?? Of course you should be using MySQL. How does this require a poll?
Click to expand...
Obviously you didn't even read my post that explained what I was asking.

I learned MySQL a long time ago because of its dominance in the market, and its free-ness. So many projects use MySQL (and usually PHP as well).

My post said:

That said, if you were to buy a web application from someone, and it needed to store data, what would you prefer?
Click to expand...
I know a lot of you guys aren't developers yourselves. Using an app that uses MySQL means you have to create databases, import schemas, and maintain a separate backup process for the databases.

I learned, and used SQLite so that I could develop a project that didn't have that overhead.

I guess I needed to spell all that out for the morons out there.
 
If I were buying an app, I'd be happy with MySQL or MS SQL Server, assuming appropriate hosting.

And by "assuming appropriate hosting," I mean that MS SQL Server is a great product and I like it a lot, but Windows-based hosting is more expensive than Linux-based, and thus I'd only go with Windows-based hosting if there were a reason to (e.g. my app was written in ASP.NET) -- I wouldn't pay the extra for Windows hosting just to use MS SQL.

PostgreSQL is a fine product, but there's very little reason to choose it over the ubiquitous MySQL.

SQLite isn't a "real" database; I consider SQLite an alternative to flat files, not an alternative to an RDBMS. The performance just isn't there on large datastores. Which isn't to say I don't use it -- just that I don't use it for anything complex enough to involve JOINs on more than two tables.
 
I learned, and used SQLite so that I could develop a project that didn't have that overhead.

I guess I needed to spell all that out for the morons out there.
Click to expand...
Must be nice to be able to backup your 8-row-data-set using "cp" instead of "mysqldump"; saves 7 letters. What you needed to spell out was that you're coding projects small enough to sit in SQLite.

When you're serious about your data -- you just told us that you aren't -- you'll use MySQL. It's really the only choice.
 
I use MySQL for all my projects, but I've used MSSQL too.. They're both great, but I prefer MySQL because it's free to use and is supported on almost all hosts
 
uplinked said:
Must be nice to be able to backup your 8-row-data-set using "cp" instead of "mysqldump"; saves 7 letters. What you needed to spell out was that you're coding projects small enough to sit in SQLite.

When you're serious about your data -- you just told us that you aren't -- you'll use MySQL. It's really the only choice.
Click to expand...
At least the morons make themselves apparent through their strawman arguments and inability to comprehend English.

Everyone else, thanks for your responses. I think we can kill this thread now..
 
Status
Not open for further replies.
Top Bottom