[Gllug] MySQL Woes

[tet at accucard.com]

>Has anybody else been flummoxed by this. Writing application code to enforce
>all the referential integrity of a database is a bit of a half arsed way of
>going about things. I notice that there is a Perl implementation, great,
>bolt on integrity.

Correct. The sinmple answer is just not to use MySQL, and use something
like PostgreSQL instead. MySQL got a lot of publicity early on for having
blindingly fast queries, which was enough to tempt people into using it,
depsite its lack of functionality. Fortunately, PostgreSQL has improved
to the point where its performance is much better, and even surpasses
MySQL in places.

Other alternatives you might want to consider are Interbase/Firebird and 
SAPDB, or Openbase at a push, but you don't get source with that, just an
almost free (beer) license.

Tet

-- 
Gllug mailing list  -  Gllug at linux.co.uk
http://list.ftech.net/mailman/listinfo/gllug