Db design question (relational vs. flat?)

This WebDNA talk-list message is from

1998


It keeps the original formatting.
numero = 17017
interpreted = N
texte = A quick db design question.... I'd like to have certain products show up in more than one product category: from: product 1 = category 2 to: product 1 = category 2 *and* category 3(Real life example; wedding music would be in both wedding and music categories.)Seems like there's (at least) 2 ways to do this, and I'd like some feedback from db gurus out there before starting:1) using the current category field, include all the appropriate category names then [search] the category field for the desired cateogry and return True when foundor2) create a separate relational db where the appropriate categories are are listed for each SKUI also thought of creating new fields for each category (ex: Wedding) and indicating T or F, but that seems to be a more inflexible and wasteful way to go...right?TIA to db design gurus...Dale Stokdyk dstokdyk@dvs.mv.com Associated Messages, from the most recent to the oldest:

    
  1. Re: Db design question (relational vs. flat?) (Grant Hulbert 1998)
  2. Re: Db design question (relational vs. flat?) (Dale Stokdyk 1998)
  3. Re: Db design question (relational vs. flat?) (PCS Technical Support 1998)
  4. Db design question (relational vs. flat?) (Dale Stokdyk 1998)
A quick db design question.... I'd like to have certain products show up in more than one product category: from: product 1 = category 2 to: product 1 = category 2 *and* category 3(Real life example; wedding music would be in both wedding and music categories.)Seems like there's (at least) 2 ways to do this, and I'd like some feedback from db gurus out there before starting:1) using the current category field, include all the appropriate category names then [search] the category field for the desired cateogry and return True when foundor2) create a separate relational db where the appropriate categories are are listed for each SKUI also thought of creating new fields for each category (ex: Wedding) and indicating T or F, but that seems to be a more inflexible and wasteful way to go...right?TIA to db design gurus...Dale Stokdyk dstokdyk@dvs.mv.com Dale Stokdyk

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:

Lookup Notfound (1998) Alternating colors (1997) When do we get to request new features? (1999) Transfer of data from Invoice to thank you templates (1998) Shopping Cart Directory (2000) IP Address Ranges in a Database. (2003) Math (1997) WebCat 5 Intranet Question (2003) Formulas.db not working (2006) Semi-OT: Update forms not working remotely (2002) Multiple catalog databases and showcart (1997) WebCatalog + Linux + ODBC + Oracle ! ? (2000) [WebDNA] El Capitan with WebDNA 8.1 fastCGI (2015) [WebDNA] Emerging from the Shell (was: unique words) (2009) Artwork (1997) [OT] WebDNA Family Album (2004) [group] ? (1997) idear about how to get SMSI to speak. (2006) Searching for a Blank Field (2000) Dates and Math - Simple Subtraction (2004)