D]>; <[EMAIL PROTECTED]>
Sent: Friday, 30 May, 2003 14:30
Subject: Re: database newbie
Foreign keys have been available in InnoDB tables since 3.23.43b.
A here's couple of pages to check out:
>From the InnoDB Manual pages:
4.3 Foreign key constraints
http://www.innodb.com/i
Foreign keys have been available in InnoDB tables since 3.23.43b.
A here's couple of pages to check out:
>From the InnoDB Manual pages:
4.3 Foreign key constraints
http://www.innodb.com/ibman.html#InnoDB_foreign_keys
>From the MySQL Manual:
1.8.4.5 Foreign Keys
http://www.mysql.com/doc/en/A
No, this was perfect. I had totally misread (I figured out after I
bothered everyone!) --it was I had always been taught and as you say.
I hope you have seen my most recent question to the list? About
manually entering the data? The short and sweet answer there be that
someone ALWAYS has to
> that is, that if the values for the field 'table1.people_id' rows is
> "1" - "50", then the field values for 'table2.location_id' (or any
> other table) cannot also be "1" - "50".
I think you're mis-interpreting the use of "values." While the actual value can
be the same between the fields (1,
Hi Ted,
Any single primary key cannot contain duplicate entries and any single table
can have only one primary key. With your example, 'table1.people_id' can
have values "1" - "50" and 'table2.location_id' have "1" - "50 at the same
time so your final statment is wrong. I assume what the book act
