Re: Database Structuring (again)
This WebDNA talk-list message is from 2003
It keeps the original formatting.
numero = 49755
interpreted = N
texte = That is certainly one of my considerations.At this point, I have started with a separate database for colors. Certain vendors have certain colors. I have built the administration interface to allow the client to manage colors by vendor. Then, when the client goes to add an item for that vendor, only the matching colors appear as checkbox options.Some of the other options don't seem to be quite as simple. Who knew a kayak paddle could be so damn complex??-----Original Message----- From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com] On Behalf Of Gary Krockover Sent: Thursday, April 24, 2003 9:05 PM To: WebDNA Talk Subject: Re: Database Structuring (again)Personally, I've always treated this type of inventory with a single database, with each instance of size or color or option being a different line in the database. Of course that means that clients have to enter nearly identical information in more than once. I'll be curious to see how others treat this type of layout.GK > I know this was just a hot debate the last couple of days. but you guys > left me behind a bit, so I'm going to ask for myself with considering > the store I am working on now. > > My client sells anything and everything having to do with outdoor > sports, from kayaks to outdoor cooking utensils to sandals to tents, > clothing and then some. With clothing, we obviously have the usual size > and color options; with sandals we have size, color, insole and outsole. > With paddles we have length, color, grip size and 1 or 2 piece sets. and > the list goes on and on for various items and their options. > > My question is to database or to multiple database. Given my > programming skills, not the greatest, but not the worst. I am leaning > more toward multiple databases. Can anyone assure me that I'm headed in > the right direction, or can anyone save me from disaster down the long > road? ------------------------------------------------------------- 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://webdna.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://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
That is certainly one of my considerations.At this point, I have started with a separate database for colors. Certain vendors have certain colors. I have built the administration interface to allow the client to manage colors by vendor. Then, when the client goes to add an item for that vendor, only the matching colors appear as checkbox options.Some of the other options don't seem to be quite as simple. Who knew a kayak paddle could be so damn complex??-----Original Message----- From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com] On Behalf Of Gary Krockover Sent: Thursday, April 24, 2003 9:05 PM To: WebDNA Talk Subject: Re: Database Structuring (again)Personally, I've always treated this type of inventory with a single database, with each instance of size or color or option being a different line in the database. Of course that means that clients have to enter nearly identical information in more than once. I'll be curious to see how others treat this type of layout.GK > I know this was just a hot debate the last couple of days. but you guys > left me behind a bit, so I'm going to ask for myself with considering > the store I am working on now. > > My client sells anything and everything having to do with outdoor > sports, from kayaks to outdoor cooking utensils to sandals to tents, > clothing and then some. With clothing, we obviously have the usual size > and color options; with sandals we have size, color, insole and outsole. > With paddles we have length, color, grip size and 1 or 2 piece sets. and > the list goes on and on for various items and their options. > > My question is to database or to multiple database. Given my > programming skills, not the greatest, but not the worst. I am leaning > more toward multiple databases. Can anyone assure me that I'm headed in > the right direction, or can anyone save me from disaster down the long > road? ------------------------------------------------------------- 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://webdna.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://webdna.smithmicro.com/
Kimberly D. Walls
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:
WebCat b13 CGI -shownext- (1997)
[WebDNA] [OT] the "Work in progress" thread. (2009)
webcat (2000)
WebCat 2.1.3 (and docs) (1998)
WebCat2 - storing unformatted date data? (1997)
[shownext max (1997)
Webdna websites (2004)
[SearchString] problem with [search] context (1997)
WebCat on Intel Core 2 macs anyone? (2007)
WC2b15 File Corruption (1997)
ShowNext Command (1997)
Help ! Frustrating Problem (1999)
The beginning (1997)
WebCommerce: Folder organization ? (1997)
Search 1 Field Twice? (2004)
WebMerchant & Online CC Auths (1999)
Caching [include] files ... (1997)
Strange Search Results (2004)
GMT question (2004)
[WebDNA] Mail with authentication (User, Password, Port) (2012)