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:

international time (1997) [WebDNA] lookup in tables defined in functions - bug? (2016) Lost and Recovered. (1998) Firesite cache vs webcat cache (1997) Anyone using [sendmail] for HTML encoded mail? (2000) Sendmail Excel attachment (2003) Finding max value for a field (1997) [shell]? (2000) WebCatalog 2.0 & WebDNA docs in HTML ... (1997) Bug? (1997) Email notification to one of multiple vendors ? (1997) Plugin or CGI or both (1997) db merge problem (2002) Fun with Dates - revisited (1997) Re:PCS Customer submissions ? (1997) Card clearance, problems - solutions? (1997) Type 11 errors setting up WebCAt 2 (1997) Quit revisited (1997) can WC render sites out? (1997) Referrer or maybe another way..... (2005)