On Thu, Sep 18, 2008 at 1:14 PM, Dan Telschow <[EMAIL PROTECTED]> wrote:
> You could add an ID to the Product Option table and include that in the
> mapping table (ProductOutlet):
>
>ProductOutlet:
> FK to Product
> FK to Outlet
> FK to ProductOption
>
You could add an ID to the Product Option table and include that in the
mapping table (ProductOutlet):
ProductOutlet:
FK to Product
FK to Outlet
FK to ProductOption
price (overrides default price)
quantity
If you do it this way, I'm
yes. Really the main differences between options at the outlet level
is going to be inventory. So amazon could have 5 size 11 air jordan's
and ebay could have 10 size 11 air jordan's.
On Thu, Sep 18, 2008 at 12:29 PM, Dan Telschow <[EMAIL PROTECTED]> wrote:
> Are we to assume that options can
Are we to assume that options can be different between Product Outlets?
James Lance wrote:
I thought I would see if any of you DBA's out there have any advice.
I'm building an inventory system that deals with inventory tracking,
and also with where inventory is being sold (outlets). I'm having
I thought I would see if any of you DBA's out there have any advice.
I'm building an inventory system that deals with inventory tracking,
and also with where inventory is being sold (outlets). I'm having a
bit of a problem with dealing with outlet over rides. For example, I
have a pair of shoes a
