Rather than starting with a simpler database, I would go with
PostgreSQL. With PostgreSQL you can start off small, but over a number
of years, it's the kind of database you can really grow into, and I
doubt you would ever outgrow PostgreSQL.
#------------------------------------------------------------------------------------
#------------------------------
Excerpt:
Other features:
In PostgreSQL, there is no built-in mechanism for limiting database
size, mostly due to the risk it implies. This is another reason, after
popularity, why the most of the web hosting companies are using
MySQL[citation needed]. Also, PgAgent a scheduling agent for PostgreSQL
allows for scheduled processes.
#-------------------------------
#-----------------------------
Excerpt:
Community:
MySQL's community is supported in part by the company's Community
Relations Team. MySQL AB has sponsored an annual User's Conference and
Expo since 2003.
PostgreSQL is a fully community supported open source project, with no
singular corporate sponsorship. Instead, companies whose business models
depend on PostgreSQL are accepted as members of the community, and code
from corporate contributors is accepted under the same terms as from any
other external contributor.
Both also have large numbers of enthusiastic supporters who are willing
to assist on a voluntary basis.
#-------------------------------
#-------------------------------
Excerpt:
Development
MySQL is owned and sponsored by a single for-profit firm, Oracle. MySQL
AB holds copyrights to most of the codebase. MySQL's corporate
management has drawn criticism for mismanagement of its development.
By contrast, PostgreSQL is not controlled by any single company, but
relies on a global community of developers and companies to develop it.
It does, however, enjoy both software development help and resource
contributions from businesses who make use of PostgreSQL database
technologies, such as EnterpriseDB. Corporate sponsors are considered
contributors roughly like any other, however, within PostgreSQL's
community-driven development model.
MySQL is an open-source PRODUCT.
Postgres is an open-source PROJECT.
— Greg Sabino Mullane , Postgres is not for sale (reprint of original
blog post)
One criticism of the MySQL development model has been the historical
reluctance of its corporate development team to accept patches from
external sources. This has prompted some to say MySQL is not a "true"
open source project. Nontrivial improvements from Google and Percona
have been accepted into the main codebase recently, though how
significant a change in external development policy this represents is
yet to be seen.
Furthermore, PostgreSQL's development team is much more accessible than
that of MySQL, and they will go as far as to provide you with a patch if
there really is a problem with the engine.
On the other hand, the MySQL team will routinely degrade bugs (to "not a
bug") without providing any solution, and accept the fact that there's a
problem and not fix it for 5 years, etc[citation needed].
http://www.wikivs.com/wiki/MySQL_vs_PostgreSQL
#-------------------------------------------------------------------------------------------
Regards,
LelandJ
On 12/13/2012 07:21 AM, Eurico Chagas Filho wrote:
What R the pros and cons ? Anyone ?
TIA, E.
--- StripMime Report -- processed MIME parts ---
multipart/alternative
text/plain (text body -- kept)
text/html
---
[excessive quoting removed by server]
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
