>
> To follow your example, I would add these other fields to the
> listings_projects table you defined below, and restructure the query
> around that?
>
> Thanks for your insight!
>
> -Erich-
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL P
around that?
Thanks for your insight!
-Erich-
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 04, 2004 11:51 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: Design Question
As posted, your data structure supports two one-to-many rela
As posted, your data structure supports two one-to-many relationships, not
the one-to-one relationships as you described. You can have multiple
Listings per Category and multiple Categories per Group. What it sounds
like you have been asked to do is to support a many-to-many relationship.
You
You are right, a comma separated "list" won't work since you won't be
able to do joins on it. To create a one to many relation, you actually
need to create another table to hold the relation.
CREATE TABLE listCatLink (
ListingID bigint(20) unsigned NOT NULL,
CategoryID int(11) NOT NULL
)
On Aug
EB> My thought was to add a new field to the listings table that would
EB> contain a comma-separated list of CategoryIDs, but something doesn't
EB> feel right about this solution.
> This would break the first normalization form and is extremely bad
Okay - I thought something was off...
> First o
Andrew Ward wrote:
> As I said, not all organisations were asked the same questions so I can't
> just put the data in directly
>
> The only way I can see of dealing with this is to create tables like
> ID,QUESTION,RESPONSE
> 1,"YEAR",2001
> 1,"SEX",1
>
> This doesn't strik
Andrew Ward writes:
> The only way I can see of dealing with this is to create tables like
> ID,QUESTION,RESPONSE
> 1,"YEAR",2001
> 1,"SEX",1
> 1,"AGE",3
> 1,"RATING A", 7
> 1,"RATING B", 6
> ...
>
> This doesn't strike me as very smart. I would greatly
Hi Jeff,
If you visit my homepage at:
www.geocities.com/hisiomara
click "Tutorials" and select the first item "Team5.com an ecommerce sample"
you will be able to see the ERD diagram that attends your ecommerce demand.
Actually will will be able to see much more.
The design is there,and I wil
hi.
the easiest way is to have
an order table:
(orderID, customer, address, etc., etc.)
a item table:
(itemID, description, price, etc.etc.)
and an orderItems table:
(orderID, itemID)
this way you can
select i.description, i.price
from order o,
item i,
orderItems oi,
where o.orde
This looks like an order-lineitem situation, which I would imagine would
look like this:
ORDERS
ORDER_ID
CUSTOMER_ID
ORDER_DATE
LINEITEM
ORDER_ID
PRODUCT_ID
LINEITEM_QUANTITY
At 02:00 PM 6/18/2001 -0500, you wrote:
>I have a design problem I was hoping some of you could help me out
>with.
10 matches
Mail list logo