>>>>> "s" == sinisa <sinisa@stripped> writes:
s> What is a use of saving a foreign key if it is not used ???
s> I can see one and only one reason. To make my optimized queries in
s> sqlclient (www.tcx.se/download_clients.html) even more optimized.
s> But the issue was referential integrity and it involves far more than
s> just saving foreing keys, which is in TODO list, by the way. Do you
s> know what a slowdown it would be for UPDATE/DELETE ... WHERE ...., if
s> full referential integrity would be implemented ??
I don't think you're getting my point: You say having the ability to
do foreign keys would slow down the server. I say no. I say that
having the ability to use foreign keys would not slow it down, but
actually *using* them would slow it down. This is ok, since there is
no penalty when I don't use them.
Please explain to me why making this feature available would slow down
MySQL when it is not in use.
It sounds to me like saying "indexes are not supported since they slow
Vivek Khera, Ph.D. Khera Communications, Inc.
Internet: khera@stripped Rockville, MD +1-301-545-6996
PGP & MIME spoken here http://www.kciLink.com/home/khera/