Hi!
>Hi!
>
>> "Arjen" == Arjen G Lentz <[EMAIL PROTECTED]> writes:
>
>
>
>>> The problem is, how would you add a new bus and a new driver to the
>>> database? Whichever one is added first, you're going to get an error
>>> because its counterpart doesn't exist yet, violating referential integ
Hi!
> "Arjen" == Arjen G Lentz <[EMAIL PROTECTED]> writes:
>> The problem is, how would you add a new bus and a new driver to the
>> database? Whichever one is added first, you're going to get an error
>> because its counterpart doesn't exist yet, violating referential integrity.
>>
>>
Hi Bennett,
- Original Message -
From: "Bennett Haselton" <[EMAIL PROTECTED]>
> In a database that enforced referential integrity, if you say that a field
> in one table is a foreign key referencing another table, then any value in
> the foreign key field in the first table must referenc
Kristian Köhntopp wrote:
> Bennett Haselton wrote:
>
>>The problem is, how would you add a new bus and a new driver to the
>>database? Whichever one is added first, you're going to get an error
>>because its counterpart doesn't exist yet, violating referential integrity.
>>
>
> I was under the
Bennett Haselton wrote:
> The problem is, how would you add a new bus and a new driver to the
> database? Whichever one is added first, you're going to get an error
> because its counterpart doesn't exist yet, violating referential integrity.
I was under the impression that databases enforced re
In a database that enforced referential integrity, if you say that a field
in one table is a foreign key referencing another table, then any value in
the foreign key field in the first table must reference an existing row in
the second table. (Right?)
But suppose you have a database storing,
