|Main Archive Page > Month Archives > spamassassin-users archives|
On Thu, 23 Jun 2011 10:29:43 +0200
Matus UHLAR - fantomas <firstname.lastname@example.org> wrote:
> On 21.06.11 15:17, David F. Skoll wrote:
> >No, not really, but MySQL is broken in so many ways I try to stay
> >away from it. Many of the design flaws in
> >http://sql-info.de/mysql/gotchas.html remain unfixed. For example,
> >even in MySQL 5.0.5, 'select 1/0;' returns NULL.
> Pardon, but which of those apply when talking about using MySQL for
> bayes database?
None, specifically. Our product already uses a database for other reasons
(PostgreSQL), so it would be silly to use *two* databases. And I would
certainly never pick MySQL as the main product database.
> 2003-02-31 is INVALID date and therefore inserting it into the
> database and selecting back CAN NOT return the same data.
My point is the INSERT should **fail**, not silently change your data.
Any non-toy DB will fail the INSERT.