Posted by: Anonymous Coward
on November 10, 2006 12:28 PM
<a href="http://sql-info.de/mysql/gotchas.html#1_13" title="sql-info.de">http://sql-info.de/mysql/gotchas.html#1_13</a sql-info.de> is a good place to start.
The correct behavior for any database is to ALWAYS throw an error and do NOTHING when it can't store exactly what you tell it to. This is especially true when you are working with financial data.
What about strict mode? Strict mode doesn't protect your data if applications can turn it off with no help from the admin.
The other gotchas are somewhat serious, but that one is a killer.
MySQL v. PostgreSQL for accounting applications
Posted by: Anonymous Coward on November 10, 2006 12:28 PMThe correct behavior for any database is to ALWAYS throw an error and do NOTHING when it can't store exactly what you tell it to. This is especially true when you are working with financial data.
What about strict mode? Strict mode doesn't protect your data if applications can turn it off with no help from the admin.
The other gotchas are somewhat serious, but that one is a killer.
#