Re: Opinion Poll Please
This WebDNA talk-list message is from 2002
It keeps the original formatting.
numero = 41447
interpreted = N
texte = It really depends on a lot of factors...* How consistent is the product offering, now and in the future? Is it a site like allwewilleversellissimpletshirts.com? Or is it rightnowwesellshirtsbutwemightexpandintocarscomputersandturnips.com?* Can a simple calculation be developed to cover all needs?* How much data would need to be duplicated with multiple product records for the different options?* Do color or size choices affect the price, or an inventory tracking system?For flexibility and to avoid duplicating data, you might consider:product.db - product ID, name, description, etc. option.db - product ID, option ID, option description, price, weight, etc.Search the product.db, then do a nested search on the option.db by product ID to get the various options available.- brianAt 1:34 PM 7/11/02, Kimberly D Ingram wrote: >When dealing with product databases that entail various prices based on >color and/or size, etc. do you find it most efficient to: > >a) Unique Product ID for each size >b) Calculated Price >c) Other, please explain.... > >Thanks, >Kim >-- <= Brian C. Fries, BrainScan Software http://www.brainscansoftware.com =>------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list
. To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/
Associated Messages, from the most recent to the oldest:
It really depends on a lot of factors...* How consistent is the product offering, now and in the future? Is it a site like allwewilleversellissimpletshirts.com? Or is it rightnowwesellshirtsbutwemightexpandintocarscomputersandturnips.com?* Can a simple calculation be developed to cover all needs?* How much data would need to be duplicated with multiple product records for the different options?* Do color or size choices affect the price, or an inventory tracking system?For flexibility and to avoid duplicating data, you might consider:product.db - product ID, name, description, etc. option.db - product ID, option ID, option description, price, weight, etc.Search the product.db, then do a nested search on the option.db by product ID to get the various options available.- brianAt 1:34 PM 7/11/02, Kimberly D Ingram wrote: >When dealing with product databases that entail various prices based on >color and/or size, etc. do you find it most efficient to: > >a) Unique Product ID for each size >b) Calculated Price >c) Other, please explain.... > >Thanks, >Kim >-- <= Brian C. Fries, BrainScan Software http://www.brainscansoftware.com =>------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/
Brian Fries
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
2.1b3 --> way slow (1997)
Document Contains No Data! (1997)
textA and Title? (1997)
Re:Emailer tracking (1997)
Generating unique SKU from [cart] - Still Stumped... (1997)
Locking up with WebCatalog... (1997)
Nested search (1997)
$Replace with [founditems] (1997)
PIXO support (1997)
Database Strategy - more... (1998)
talking to MacAuthorize (1997)
Time Display from Database (1997)
Wanted: Broader string manipulation functions (1997)
SiteEdit NewFile.html ? (1997)
Still search problems! (1999)
Signal Raised (1997)
[cart] clarification... (1997)
Emailer Q (2002)
Banner DNA (1997)
Listserver problem (1997)