Re: FLASH: Database Structure

[james]

I'd have to look into a few online stores I've dealt

with in the past, but off the top of my head, I

believe there was an attibutes table that was linked

by product ID.  So, within that attibutes table you

would have as many attributes as you wanted associated

with that item. (size, color, material, etc)  And yes,

as in real retail, I belive each unique size/color,

etc of an item as it's own Product ID or SKU number I

think it is.


Then, when you build your search or product ordering

pages, have them dynamically read that attribute table

to figure out what attributes apply to the product

they are working with.  You wouldn't want size for

example with a coffee mug.  Therefore, that would have

to read the attributes table to build the search and

order forms.


Again, this is off the top of my head, and my brain

likes to shut down on Saturday, so it may not be much

help.  



James


--- Cheri Harder <

chericahome [dot] com

> wrote:


?In other words, are there different part

> numbers for each

> combination of option, so each gets its own line of

> data?  Or is there an

> "options" column or two or three, where the code in

> that line of data refers

> to a "dictionary" table of options...

> sizes, colors....

> 


__________________________________________________

Do You Yahoo!?

Talk to your friends online with Yahoo! Messenger.

http://im.yahoo.com


flasher is generously supported by...

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

     flashforward2000 and The Flash Film Festival

  "The World�s Premier Flash Solutions Conference and Expo"

 March 27-29, Nob Hill Masonic Center, San Francisco, California


-Register before Feb 25 and save $200!!-- www.flashforward2000.com

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

To unsubscribe or change your list settings go to

http://www.chinwag.com/flasher or email

helpchinwag [dot] com