I've always been a believer in avoiding sql procedures, for the main
reason that I want to be as database-independent as possible. I know it
is less efficient, but being able to switch between MySQL, Postgre, and
the new freebies from IBM, Oracle, and Microsoft is a strong advantage
from the bu
le.
Keith
In theory, theory and practice are the same;
in practice they are not.
On Mon, 20 Mar 2006, Martijn Tonies wrote:
> To: mysql@lists.mysql.com
> From: Martijn Tonies <[EMAIL PROTECTED]>
> Subject: Re: Discussion: the efficiency in using foreign keys
>
> Hi,
>
&g
Hi,
> This is a fundamental concept in RDBMS: the use of foreign keys in
> database design.
>
> I'd just like to poll the community here, on whether it is a best
> practice, or practically essential to 'link' related tables by use of
> foreign keys.
>
> For myself, I usually do all the validi
Hello Keith,
Thanks for responding. I was actually referring to the subject of using
foreign keys, as opposed to leaving it to the calling application to do
the necessary checks. In particular issues of performance, efficiency
etc. IMHO, foreign keys add 'strictness' to the consistency of rela
IMHO I think you will find that there is a balance between
the speed of opening and reading/writing several related
smaller tables connected by FK's, rather than one mega-sized
gigantic table.
How do you normalise a table without using FK's.
Your right, MySQL does not currently do any checking
