My only work with databases is through ColdFusion, largely
Access.
In designing the tables, Access forces you to define a Primary
Key, but I've only ever used the Relationships view where
you define the actual relationships for visualisation purposes.
Most of the sites I've done have been
: Gyrus [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 09, 2002 10:31 AM
To: CF-Talk
Subject: Defining internal DB relationships necessary?
My only work with databases is through ColdFusion, largely
Access.
In designing the tables, Access forces you to define a Primary
Key, but I've only ever
PROTECTED]
To: CF-Talk [EMAIL PROTECTED]
Sent: Wednesday, January 09, 2002 9:31 AM
Subject: Defining internal DB relationships necessary?
My only work with databases is through ColdFusion, largely
Access.
In designing the tables, Access forces you to define a Primary
Key, but I've only ever
www.macromedia.com
- Original Message -
From: Gyrus [EMAIL PROTECTED]
To: CF-Talk [EMAIL PROTECTED]
Sent: Wednesday, January 09, 2002 7:31 AM
Subject: Defining internal DB relationships necessary?
My only work with databases is through ColdFusion, largely
Access.
In designing the tables, Access
Are you sure that the relationships are only used in the Access GUI? My
understanding is that they were true constraints.
You're right, I believe - only I've never had a single problem
so far with not defining them inside the DB (apart from PK's,
which Access forces, and I've got into the
, and Implementation 7th
edition, David M. Kroenke, Copyright 2000, Prentice Hall,
http://www.prenhall.com/kroenke)
HTH,
Dina
- Original Message -
From: Gyrus
To: CF-Talk
Sent: Wednesday, January 09, 2002 9:31 AM
Subject: Defining internal DB relationships necessary?
My only
PROTECTED]
To: CF-Talk [EMAIL PROTECTED]
Sent: Wednesday, January 09, 2002 8:52 AM
Subject: Re: Defining internal DB relationships necessary?
Are you sure that the relationships are only used in the Access
GUI? My
understanding is that they were true constraints.
You're right, I believe
At 03:31 PM 01/09/2002 +, you wrote:
My only work with databases is through ColdFusion, largely
Access.
In designing the tables, Access forces you to define a Primary
Key, but I've only ever used the Relationships view where
you define the actual relationships for visualisation purposes.
Well here is my thought. As far as my DB is concerned I fully use
creating a pri key and foreign key relationships where needed on all my
tables. This helps so much in avoiding someone delteting something from
one table that relies on something in another table.
As I said, I do rigorous
Brown
- Original Message -
From: Gyrus [EMAIL PROTECTED]
To: CF-Talk [EMAIL PROTECTED]
Sent: Wednesday, January 09, 2002 9:49 AM
Subject: Re: Defining internal DB relationships necessary?
Well here is my thought. As far as my DB is concerned I fully use
creating a pri key and foreign
At 05:49 PM 01/09/2002 +, you wrote:
Well here is my thought. As far as my DB is concerned I fully use
creating a pri key and foreign key relationships where needed on all my
tables. This helps so much in avoiding someone delteting something from
one table that relies on something in
You're right, not defining the relationships won't cause anything to crash,
but can compromise the integrity of your database
- Original Message -
From: Gyrus [EMAIL PROTECTED]
To: CF-Talk [EMAIL PROTECTED]
Sent: Wednesday, January 09, 2002 10:52 AM
Subject: Re: Defining internal DB
[EMAIL PROTECTED]
To: CF-Talk [EMAIL PROTECTED]
Sent: Wednesday, January 09, 2002 11:49 AM
Subject: Re: Defining internal DB relationships necessary?
Well here is my thought. As far as my DB is concerned I fully use
creating a pri key and foreign key relationships where needed on all my
tables
to maintain.
Mark
-Original Message-
From: Gyrus [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 09, 2002 12:50 PM
To: CF-Talk
Subject: Re: Defining internal DB relationships necessary?
Well here is my thought. As far as my DB is concerned I fully use
creating a pri key and foreign key
14 matches
Mail list logo
