Janine Jakim wrote:
1. One student can be working on many goals so I have 1 one to many
relationships.
2. Each goal needs graded every marking period (up to 6 times a
year)- these are not traditioanl grades but a long comments piece) So
goals have a one to many relationship with the
Ack. Always keep one-to-many stuff relational on general principles. Its not that
much extra work.
---
Matt Robertson, MSB Designs, Inc.
http://mysecretbase.com - Retail
http://foohbar.org - ColdFusion Tools
---
21, 2002 4:10 PM
To: CF-Talk
Subject: Re: OT: Database design question
Janine Jakim wrote:
1. One student can be working on many goals so I have 1 one to many
relationships.
2. Each goal needs graded every marking period (up to 6 times a
year)- these are not traditioanl grades but a long
At 03:59 PM 11/21/2002 -0500, you wrote:
hmmm- I am very into keepting my database relational, but am wondering what
the best route for thi particular issue is...
Heres' the scoop
1. One student can be working on many goals so I have 1 one to many
relationships.
I suspect this is a many to
You conceptually have 2 different prices
1 The Current Price usually stored in the Product File
2 The Order price (The Current Price when this order was filled)
usually
stored in an order item file along with Qty (extended Item
Amount Optional)
1. is a status
Agreed. Store the price the product was sold at in your orderitem table.
You conceptually have 2 different prices
1 The Current Price usually stored in the Product File
2 The Order price (The Current Price when this order was filled)
usually
stored in an order
This is how I would handle it. It sounds like a standard many-to-many
relationship.
At 10:17 AM 01/30/2002 -0800, you wrote:
I'm putting together a new database for a fairly substantial application I
need to build.
Here is the kind of information I need to store:
-- Registration of
.
Doug Brown
- Original Message -
From: Jeffry Houser [EMAIL PROTECTED]
To: CF-Talk [EMAIL PROTECTED]
Sent: Wednesday, January 30, 2002 10:34 AM
Subject: Re: (OT) Database Design Question
This is how I would handle it. It sounds like a standard
many-to-many
relationship
that come out of Berkeley: LSD and [Unix]
BSD. We don't believe this to be a coincidence.
Doug Brown
- Original Message -
From: Jeffry Houser [EMAIL PROTECTED]
To: CF-Talk [EMAIL PROTECTED]
Sent: Wednesday, January 30, 2002 10:34 AM
Subject: Re: (OT) Database Design Question
That looks like it would work fine. I prefer to use two
tables instead of 3 myself. less joining.
[user]
id[PK]
name
address
[category]
id PK
user_id (FK_USER.ID)
cat_name
In your model, a category could only belong to one user.
Dave Watts, CTO, Fig Leaf Software
don't believe this to be a coincidence.
Doug Brown
- Original Message -
From: Jeffry Houser [EMAIL PROTECTED]
To: CF-Talk [EMAIL PROTECTED]
Sent: Wednesday, January 30, 2002 10:34 AM
Subject: Re: (OT) Database Design Question
This is how I would handle it. It sounds like a standard
11 matches
Mail list logo
