Re: Enforcing integrity of Foreign Keys

"Zachary Agatstein" <[EMAIL PROTECTED]> wrote: > Well, in order to enforce referential integrity, I converted the tables to > InnoDB. But referential integrity is still not being enforced. I use > mysql version 3-23-54-nt, and the tables are generated through the use of > dbdesigner (ver. 4.0

Re: Enforcing integrity of Foreign Keys

Well, in order to enforce referential integrity, I converted the tables to InnoDB. But referential integrity is still not being enforced. I use mysql version 3-23-54-nt, and the tables are generated through the use of dbdesigner (ver. 4.0.5.6 beta). Here is a snippet of a "create" script: ==

Re: Enforcing integrity of Foreign Keys

"Zachary Agatstein" <[EMAIL PROTECTED]> wrote: > A very simple question: > > If I have a table A with PRIMARY KEY K, > and table B which has a column C defined as a FOREIGN KEY F referencing > table A.K, > > then, I would expect, C can only take a value from those already existing in > table A

Re: Enforcing integrity of Foreign Keys

Which kind of tables do you have? InnoDB tables enforce foreign key integrity, MyISAM tables do not. From the manual : | In MySQL 3.23.44 or later, InnoDB tables support checking of foreign key | constraints. ... For other storage engines, M

Enforcing integrity of Foreign Keys

A very simple question: If I have a table A with PRIMARY KEY K, and table B which has a column C defined as a FOREIGN KEY F referencing table A.K, then, I would expect, C can only take a value from those already existing in table A column K. So, let's assume, for simplicity's sake, table A has