Re: Database Sizes

This WebDNA talk-list message is from

2000

It keeps the original formatting. numero = 35089
interpreted = N
texte = You need to create one item by color.Unless you come with a computer configurator (a build your own computertool), that would require you to create hundreds of combination in advance(then you would use another method), all you have to do is create one itemby solution possible.T-Shirt database:SKUDescriptionSizeColor...TS_MTNB_SWMetallica: Napster Bad T-ShirtSWhite...TS_MTNB_MWMetallica: Napster Bad T-ShirtMWhite...TS_MTNB_LWMetallica: Napster Bad T-ShirtLWhite...TS_MTNB_XLWMetallica: Napster Bad T-ShirtXLWhite...TS_MTNB_SBMetallica: Napster Bad T-ShirtSBlack...TS_MTNB_MBMetallica: Napster Bad T-ShirtMBlack...TS_MTNB_LBMetallica: Napster Bad T-ShirtLBlack...TS_MTNB_XLBMetallica: Napster Bad T-ShirtXLBlack...Then, make a search on the database, summarizing by description. Inside ofeach item, show each possible combination by making a search like:eqDescriptiondatarq=[url][Description][/url]Using the rq parameter will allow you to search on other fields at thesame time.You can monitor the pricing and availability for each combination. For somereason, the Black shirts might sell more than the White ones.And you might sell more XL as well.Unless you unique buyer is Lars Ullrich.You might have to think of a XXS category.----- Original Message -----From: Mac Sherwood To: WebCatalog Talk Sent: Monday, July 24, 2000 10:56 AMSubject: Re: Database Sizes> They should be able to order one product and choose their size and color> then add to cart. Pricing remains the same.>> How would this be reflected in WEBDNA?>> Thanks.>> mark>>> > Depends: is the user ever going to be able to order more than one size> > or color of a given object at the same time? If the answer is no, you> > can use a single SKU for all sizes, and store size and color in texta,> > textb, etc.> >> > If the user can buy the same object in more than one color or size at> > the same time, you will need to have a separate SKU for each possible> > combination. I would create one table with SKU_COLOR_SIZE and each> > column individually, like this:> >> > SKU_COLOR_SIZESKUCOLORSIZE> >> > and update it as you add items. Then if all like objects are priced> > the same, you can store price/description/etc in a database with one> > record for each SKU. The user selects model, color and size, and you> > add that to the line items using the above database as the master.> >> > HTH> >> > John Peacock> >> >> > Mac Sherwood wrote:> >>> >> What is the best way to have WebCatalog create sizes/colors within a> >> product's field?> >>> >> Thanks> >>> >> mark> >>> >> -------------------------------------------------------------> >> 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/> >> > -------------------------------------------------------------> > 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/>>> -------------------------------------------------------------> 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/-------------------------------------------------------------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:

Re: Database Sizes (Nicolas Verhaeghe 2000)
Re: Database Sizes (Mac Sherwood 2000)
Re: Database Sizes (Mac Sherwood 2000)
Re: Database Sizes (Nicolas Verhaeghe 2000)
Re: Database Sizes (John Peacock 2000)
Re: Database Sizes (Mac Sherwood 2000)
Re: Database Sizes (Nicolas Verhaeghe 2000)
Database Sizes (Mac Sherwood 2000)

You need to create one item by color.Unless you come with a computer configurator (a build your own computertool), that would require you to create hundreds of combination in advance(then you would use another method), all you have to do is create one itemby solution possible.T-Shirt database:SKUDescriptionSizeColor...TS_MTNB_SWMetallica: Napster Bad T-ShirtSWhite...TS_MTNB_MWMetallica: Napster Bad T-ShirtMWhite...TS_MTNB_LWMetallica: Napster Bad T-ShirtLWhite...TS_MTNB_XLWMetallica: Napster Bad T-ShirtXLWhite...TS_MTNB_SBMetallica: Napster Bad T-ShirtSBlack...TS_MTNB_MBMetallica: Napster Bad T-ShirtMBlack...TS_MTNB_LBMetallica: Napster Bad T-ShirtLBlack...TS_MTNB_XLBMetallica: Napster Bad T-ShirtXLBlack...Then, make a search on the database, summarizing by description. Inside ofeach item, show each possible combination by making a search like:eqDescriptiondatarq=[url][Description][/url]Using the rq parameter will allow you to search on other fields at thesame time.You can monitor the pricing and availability for each combination. For somereason, the Black shirts might sell more than the White ones.And you might sell more XL as well.Unless you unique buyer is Lars Ullrich.You might have to think of a XXS category.----- Original Message -----From: Mac Sherwood To: WebCatalog Talk Sent: Monday, July 24, 2000 10:56 AMSubject: Re: Database Sizes> They should be able to order one product and choose their size and color> then add to cart. Pricing remains the same.>> How would this be reflected in WEBDNA?>> Thanks.>> mark>>> > Depends: is the user ever going to be able to order more than one size> > or color of a given object at the same time? If the answer is no, you> > can use a single SKU for all sizes, and store size and color in texta,> > textb, etc.> >> > If the user can buy the same object in more than one color or size at> > the same time, you will need to have a separate SKU for each possible> > combination. I would create one table with SKU_COLOR_SIZE and each> > column individually, like this:> >> > SKU_COLOR_SIZESKUCOLORSIZE> >> > and update it as you add items. Then if all like objects are priced> > the same, you can store price/description/etc in a database with one> > record for each SKU. The user selects model, color and size, and you> > add that to the line items using the above database as the master.> >> > HTH> >> > John Peacock> >> >> > Mac Sherwood wrote:> >>> >> What is the best way to have WebCatalog create sizes/colors within a> >> product's field?> >>> >> Thanks> >>> >> mark> >>> >> -------------------------------------------------------------> >> 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/> >> > -------------------------------------------------------------> > 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/>>> -------------------------------------------------------------> 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/-------------------------------------------------------------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/ Nicolas Verhaeghe

DOWNLOAD WEBDNA NOW!

Re: Database Sizes

2000

Top Articles:

Related Readings: