<!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>MySQL Woes</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=2 FACE="Arial">I am trying to implement a database and thought that with all the hype MySQL gets that I could do it on that. Much to my dismay I have just noticed that.</FONT></P>
<P><FONT SIZE=2 FACE="Arial">1. No method for referential Integrity.</FONT>
</P>
<BR>
<P><FONT SIZE=2 FACE="Arial">Fair enough no referential integrity I'll use stored procedures to enforce some kind of logic. No wait </FONT>
</P>
<P><FONT SIZE=2 FACE="Arial">2. No Stored Procedures</FONT>
</P>
<P><FONT SIZE=2 FACE="Arial">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.</FONT></P>
<BR>
<P><FONT SIZE=2 FACE="Arial">Harry </FONT>
</P>
<P><FONT SIZE=2 FACE="Arial">(Bruce! If you say anything like, I told you so, or, You should have listened!!!, You will find out what the infamous "Bung Ring Expander" is used for.)</FONT></P>
<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>