Mark Sargent <[EMAIL PROTECTED]> wrote on 04/06/2006 10:45:43 PM:
> [EMAIL PROTECTED] wrote:
> > I agree with the basic design: one table for all of your basic objects
> > (shirts, pants, coats, shoes, etc), one table for all of your
attributes
> > (see Barry's response), a sku table equating
Hi All,
I forgot to mention, although a general range exists for say, Jeans,
36-44 for existence, there are variations for different areas for
different labels. Example, a 34 for Jean A is say 42 in the waist, but
Jean B is 44, within the same maker. I find that as making it more
complexed. A
Hi All,
what do you all think about using OSCommerce for this? I have no
previous experience with it, but have been looking at it the last 2days.
This company has been playing with it, but they were concerned with the
many attributes and the requirement of inputting so many records as I
origi
[EMAIL PROTECTED] wrote:
I agree with the basic design: one table for all of your basic objects
(shirts, pants, coats, shoes, etc), one table for all of your attributes
(see Barry's response), a sku table equating objects (differentiated by
their attributes) and their inventory quantities (on h
Barry <[EMAIL PROTECTED]> wrote on 04/06/2006 03:52:53 AM:
> Mark Sargent wrote:
> > Hi All,
> >
> > I have the job of creating a DB for an online clothing company. I have
> > some experience with relational design and sql and php. I'm stumped as
> > they have products that contain numerous a
Hello Mark,
What exactly is your question?
How to design the tables for the different types of clothing?
Martijn Tonies
Database Workbench - development tool for MySQL, and more!
Upscene Productions
http://www.upscene.com
My thoughts:
http://blog.upscene.com/martijn/
Database development questio
Mark Sargent wrote:
Hi All,
I have the job of creating a DB for an online clothing company. I have
some experience with relational design and sql and php. I'm stumped as
they have products that contain numerous attributes, and are wishing to
get away, if possible, with entering separate recor
Hi All,
I have the job of creating a DB for an online clothing company. I have
some experience with relational design and sql and php. I'm stumped as
they have products that contain numerous attributes, and are wishing to
get away, if possible, with entering separate records for each and every
