Re: How to represent a Specification in the Relational model

Thanks for the replies. I see how this will solve problem #2. But what's the solution to problem #1? An order can be specified either for a product (Toaster), without specifying a particular subproduct (any Toaster); or an order can be specified for a particular subproduct (GE Toaster 3000). How are both of those orders modelled?

Bob Badour wrote:
> Meanwhile, you have quickly and easily described an entire solution for
the allegedly complex solution.

Neo wrote:
> > 1) An order may be for a product (eg Toaster), or for a subproduct (GE
> > Toaster 3000).
> >
> > 2) An order may be marked Rush. If it's marked Rush, you may optionally
> > specify a reason (from a list).
>
> How about this schema?
>
> T_Category (id, name, ...)
> T_Product (id, name, ...)
> T_ProductCat (prod_id, cat_id)
>
> T_Order (id, name, ... )
> T_OrderProduct (order_id, prod_id)
>
> T_RushJustification (id, descr, ...)
> T_OrderRush (order_id, rush_id)
Received on Wed Jan 10 2007 - 06:17:34 CET