Lots of comments on these questions here:
http://slashdot.org/articles/00/06/28/1454220.shtml
I'm no expert, but my impressions:
a. MySQL recently supports transactions. I don't know if this support is
in a current 'stable' release yet or not.
b. You can't do sub-queries.
c. Locking mechanisms are pretty weak.
The consensus seems to be that MySQL is built for speed and not for
situations where you need rock-solid data integrety. So if you're serving
dynamic web content, MySQL is great. For a sales processing database you
might want to look at something like Postgres.
At 04:55 PM 6/29/00 -0400, you wrote:
>Hello,
>
>We are about to start a fairly large project using mysql on Unix
>as our DB. I hear there is no transaction support, you can't do
>'sub selects' (Is that the same thing as a sub-query?), and that it is
>in some way 'single threaded' and/or unsuitable for multiuser
>environments...?
>Could someone with some experience explain/clarify these things and
>possibly provide some examples of where we might run into trouble...?
>
>Thanks in advance for any help you can offer.
>
>Mike Bannister
>geekteam.com
>
>------------------------------------------------------------------------------
>Archives: http://www.eGroups.com/list/cf-talk
>To Unsubscribe visit
>http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or
>send a message to [EMAIL PROTECTED] with 'unsubscribe' in
>the body.
------------------------------------------------------------------------------
Archives: http://www.eGroups.com/list/cf-talk
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
