Differences between version 34 and predecessor to the previous major change of PostgresVsMysql.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 34 | Last edited on Saturday, May 6, 2006 10:28:57 pm | by LawrenceDoliveiro | Revert |
| Older page: | version 33 | Last edited on Thursday, January 12, 2006 6:22:35 pm | by ChristopherCashell | Revert |
@@ -50,10 +50,9 @@
[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. If you're storing data in
a database surely you want your
- data to be correct?
+ [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).
__SPECIAL SERVER SIDE FEATURES__:
[PostgreSQL] by default doesn't listen on the network as a security feature.
