Differences between version 36 and predecessor to the previous major change of PostgresVsMysql.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 36 | Last edited on Tuesday, March 31, 2009 4:20:21 pm | by LawrenceDoliveiro | Revert |
| Older page: | version 35 | Last edited on Tuesday, December 19, 2006 9:27:55 am | by MatthiasDallmeier | Revert |
@@ -48,15 +48,13 @@
__DATA INTEGRITY__:
[PostgreSQL] takes a hit because it wants your data to be correct by enforcing constraints.
- [MySQL] has no
constraints and in the 3
.x tree (which is the most widely used) has no
- provisions for transactions or rollbacks
. [PostgreSQL
] exits gracefully on diskfull,
- [MySQL] corrupts your tables (LawrenceDoliveiro would like to see some evidence to back this up, having personally encountered a situation where MySQL coped quite gracefully with a disk-full situation with about a million records in the database)
.
+ [MySQL] [
has limited referential
constraints|http://dev
.mysql
.com/doc/refman/5./en/create-table.html
].
__SPECIAL SERVER SIDE FEATURES__:
- [PostgreSQL]
by default doesn
't listen on the network as a security feature.
+ Both
by default don
't listen on the network as a security feature.
[PostgreSQL]'s security is far more advanced than [MySQL]'s
allowing things like IDENT auth etc.
__LOCKING AND CONCURRENCY SUPPORT__:
@@ -72,12 +70,10 @@
__ALTER TABLE__:
[PostgreSQL]'s ALTER TABLE is lacking compared to [MySQL].
- However
, a carefully designed schema should preclude any need for altering
- types of columns, though
in practice requirements change during the life of a DataBase.
- Changing types of columns can have wide ranging effects as the rest of your application
- may need to be changed on the fly somehow, so changes need to be made carefully
.
+ In theory
, a carefully designed schema should preclude any need for altering
+ types of columns, but
in practice requirements change during the life of a DataBase.
[PostgreSQL] requires to ALTER TABLE SET NOT NULL in an extra step after adding a
column to allow you to put proper data into the new column before the <tt>NOT NULL</tt>
constraint is added.
@@ -102,4 +98,5 @@
* [MySQL] has a page where it will unit test the [DBMS]s of your choice and give [a breakdown on whether the feature was available | http://www.mysql.com/information/features.html].
* An indepth article on [real world performance testing of MySQL and PostgreSQL | http://www.phpbuilder.com/columns/tim20000705.php3?page=1].
* [Issues to be aware of when using MySQL | http://sql-info.de/mysql/gotchas.html]
* [DB comparison against standards|http://troels.arvin.dk/db/rdbms/]
+* Reuven Lerner’s description of [MySQL|http://www.linuxjournal.com/article/9571], [PostgreSQL|http://www.linuxjournal.com/article/9618], and [comparison of the two|http://www.linuxjournal.com/article/9649]
