Ivan Jager <[EMAIL PROTECTED]>
> Joe Brenner wrote:
> > It's not clear to me whether or not MySQL is a good choice
> > for "e-commerce", strictly speaking. It's a decent choice
> > for running a website like slashdot, where they have to
> > serve up a lot of data fast, but no one really fundamentally
> > cares about the data all that much (you lose a couple of
> > messages, that's an annoyance, not an "I'll take you to
> > court for this" problem).
> >
> > There at least used to be problems with MySQL lacking
> > transaction support[1], and if I remember correctly there was a
> > problem with keeping it up 24/7 (I think you needed to go
> > off-line to do backups).
> >
> > I'm not sure what the status is of these problems at the
> > moment. Supposedly they've hacked in some sort of
> > transaction support, via the Berkeley DB code (though I
> > think this means that there are two kinds of tables in MySQL
> > now, faster ones without transaction support, and slower
> > ones that have it).
> >
> > Anyway, if you're really doing E-commerce, I would strongly
> > suggest using postgresql, which is arguably still the only
> > "real" open source database. (And it's quite possible that
> > you really should just bite the bullet and pay for an Oracle
> > license.)
> >
> > [1] Transaction support is important to make sure that things
> > don't get royally screwed up if something gets interrupted
> > in the middle, e.g. you don't want to bill someone and
> > forget to ship, or ship something and forget to bill.
>
> What are the main differences between MySQL and postgresql? I would like
> to keep squid's logs in a database to be able to make some queries and
> all that. :)
>
> I was going to use postgres, but now that MySQL is Free it makes me
> wonder...
>
> What are the advantages/disadvantages of current versions of postgres
> and MySQL?
I don't know what to tell you outside of what I just said.
Fans of MySQL love to talk about how it's "FAST!".
Fans of Postgresql are inclined to talk about reliability,
and SQL compatibility.
If I understand the application that you have in mind, there
are probably few technical differences big enough to settle
the issue.
The GPL'd MySQL is only a beta-version at the moment, and
the postgresql team has been progressing really
rapidly. The beta period for 7.0 went really smoothly, and
a stable version of 7.0 is out now. All expectations are
that they'll meet or surpass Borland's Inprise by 7.1 or 7.2
(note: Borland keeps saying they're going to open up
Inprise, but that seems to have stalled out, at least for
now).
MySQL evidentally has a number of useful "features", like
additional data types, a LIMIT on select statements that
returns a fixed number at a time, and so on. To my eye,
this is just embrace-and-extend, and if you code to rely on
a MySQL feature, you'll never be able to switch databases
again.
Postgresql is closer to being SQL compliant, so you can
probably use a standard reference like "Practical SQL" to
learn how to use it (there's also a book in the works from
Bruce Momjian, currently available online at
http://www.postgresql.org). In the case of MySQL, you
probably need to find a mysql-specific book (a number of
these are pointed at on http://www.mysql.com).
Obviously I'm a postgresql booster here, but there are
reasons I might run MySQL... for example if I wanted to
run a package that was designed to work with it, like the
slashcode or (I think) bugzilla.
_______________________________________________
Redhat-devel-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-devel-list
