[Gllug] MySQL Woes

[Matthew Kirkwood]

On Wed, 12 Jun 2002, Jackson, Harry wrote:

> I am trying to create an application that can be used with any
> database. If MySQL is going to be one of these and it will because of
> its popularity in the GNU world then the application code will have to
> enforce referential integrity. This means that if we enforce the
> integrity at the application level do we duplicate the rules at the
> Postgres back end or not. Personally I wouldn't because it will be
> duplication of effort but we will end up with a top heavy application
> that is already suffering with scalability issues.

If scalability is at all a concern, you'd be wiser to ignore
MySQL from the start.

> Postgres is a ODBMS not an RDBMS. Not entirely sure what the
> implications are as far as design are concerned but I imagine it
> would be a bit different.

Actually, the "O" bits (with the exception of data-type
extensibility) are probably best ignored in most cases.
Postgres is a mature product, but nobody seems really
interested in the object stuff, and the semantics are a
bit vague.

Matthew.


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