<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2653.12">
<TITLE>RE: [Gllug] MySQL Woes</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=2>> -----Original Message-----</FONT>
<BR><FONT SIZE=2>> From: Paul Brazier [<A HREF="mailto:pbrazier@cosmos-uk.co.uk">mailto:pbrazier@cosmos-uk.co.uk</A>]</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Try PostgreSQL. I've not used it but I believe it does more of the</FONT>
<BR><FONT SIZE=2>> "proper" SQL RDBMS stuff than MySQL.</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> I think MySQL is for when you want speed and aren't so worried about</FONT>
<BR><FONT SIZE=2>> referential integrity etc.</FONT>
</P>
<P><FONT SIZE=2>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.</FONT></P>
<P><FONT SIZE=2>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.</FONT></P>
<P><FONT SIZE=2>Harry </FONT>
<BR><FONT SIZE=2>To keep it a little on topic, I cannot believe that I have become a victim of an open source applications popularity.</FONT>
</P>
<BR>
<CODE><FONT SIZE=3><BR>
<BR>
*************************************************************************************<BR>
COLT Telecommunications<BR>
Registered in England No. 2452736<BR>
Registered Office: Bishopsgate Court, 4 Norton Folgate, London E1 6DQ<BR>
Tel. +44 20 7390 3900<BR>
<BR>
This message is subject to and does not create or vary any contractual<BR>
relationship between COLT Telecommunications, its subsidiaries or <BR>
affiliates ("COLT") and you. Internet communications are not secure<BR>
and therefore COLT does not accept legal responsibility for the<BR>
contents of this message. Any view or opinions expressed are those of<BR>
the author. The message is intended for the addressee only and its<BR>
contents and any attached files are strictly confidential. If you have<BR>
received it in error, please telephone the number above. Thank you.<BR>
*************************************************************************************<BR>
</FONT></CODE>
</BODY>
</HTML>