Federico Sevilla III writes:
> Hi there everyone!
>
> I know I am running the risk of starting some sort of "war" here. If I can find
> information answering my question somewhere on the Internet, please let me know
> of the URL.
http://photo.net/sql/transactions.html
More than anything, you need to read a good introductory text on database
theory, specifically the ACID (Atomicity, Consistency, Isolation,
Durability) test for transactions.
> In what ways is MySQL better than PostgreSQL, and in what ways is it the other
> way around? This also brings us to: for what applications (real world) will
> MySQL be a better solution compared to PostgreSQL, and for what applications
> will it be the other way around?
MySQL, as we have already discussed before, is a data engine that
understands SQL. It does not support transactions, subselects, views, or
outer joins. It does not support the full range of relational operations.
PostgreSQL is a full featured RDBMS that supports transactions, subselects,
views and (coming soon) outer joins. It's much closer to fulfulling the
ACID requirements than MySQL is, but it's not quite there yet either (it's
missing the C), as of 6.5.*.
> No, I don't need this to answer some paper in school (hahaha). I need some help
> deciding which to use for the office. :-)
Again, read up on transactions before fooling around with important data.
Then you'll be in a position to intelligently decide on what software to
use.
Brian
--
Brian Baquiran <[EMAIL PROTECTED]>
http://www.baquiran.com/
AIM: bbaquiran
-
Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph
To leave: send "unsubscribe" in the body to [EMAIL PROTECTED]
