Re: products db philosophy

This WebDNA talk-list message is from

2001


It keeps the original formatting.
numero = 39797
interpreted = N
texte = If there is structure to the description, like sentences or paragraphs that get re-used for lots of products, you can save some space by creating a separate db for description pieces, and a database to associate pieces with products, including what order they should appear.Products would look like it does. Description pieces would look like:ID Desc 01 Includes carrying case. 02 3 Year Warranty 03 5 Year Warranty 04 Only available in Ohio ..etc..A separate db would associate what description pieces go with what product, and in what order:ProductID DescriptionID Order 4455 01 1 4455 03 2 4460 01 1 4460 02 2 4460 04 3 ..etc..It's a hassle to set up, and you will need to make administration pages or come up with some reliable way to manage records in three dbs instead of just one, but if your descriptions tend to be long and include text that is largely the same for a lot of products, this approach can save some space.Remember though that text is usually small. It's probably orders of magnitude smaller than product images, for example, and disk space is cheap.Pat> Hello, > I'm looking for some advice from the admins here that might have gone through > this so I don't have to learn the hard way. (like I usually do) > > I have a products database. (will be approx a Meg in size or more with the > following) > > In the product db I have a couple short description fields. I also have one > larger description field. > This field could have text that is maybe up to a paragraph long. > > The only place this long description will be used is in the product detail > area. > I am guessing this larger field could tripple the size of our products > database. (perhaps 3 megs?) > > My question is: > In your opinion should I separate this portion out to a detail.db? > > Our Server has plenty of RAM and is a G4 PPC so I am not sure if there will be > a speed improvment separating them or not. > > Thanks in Advance for your comments. > > > -- Donovan D. Brooke > Systems Administrator/ > Assc. Art Director > Epsen Hillmer Graphics > > > I know I'm making progress when I look at the questions I have > asked in the past and think to myself... how stupid was that > > > ------------------------------------------------------------- > 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:

    
  1. Re: products db philosophy (Donovan Brooke 2001)
  2. Re: products db philosophy (Andrew Simpson 2001)
  3. Re: products db philosophy (John Peacock 2001)
  4. Re: products db philosophy (Pat McCormick 2001)
  5. products db philosophy (Donovan Brooke 2001)
If there is structure to the description, like sentences or paragraphs that get re-used for lots of products, you can save some space by creating a separate db for description pieces, and a database to associate pieces with products, including what order they should appear.Products would look like it does. Description pieces would look like:ID Desc 01 Includes carrying case. 02 3 Year Warranty 03 5 Year Warranty 04 Only available in Ohio ..etc..A separate db would associate what description pieces go with what product, and in what order:ProductID DescriptionID Order 4455 01 1 4455 03 2 4460 01 1 4460 02 2 4460 04 3 ..etc..It's a hassle to set up, and you will need to make administration pages or come up with some reliable way to manage records in three dbs instead of just one, but if your descriptions tend to be long and include text that is largely the same for a lot of products, this approach can save some space.Remember though that text is usually small. It's probably orders of magnitude smaller than product images, for example, and disk space is cheap.Pat> Hello, > I'm looking for some advice from the admins here that might have gone through > this so I don't have to learn the hard way. (like I usually do) > > I have a products database. (will be approx a Meg in size or more with the > following) > > In the product db I have a couple short description fields. I also have one > larger description field. > This field could have text that is maybe up to a paragraph long. > > The only place this long description will be used is in the product detail > area. > I am guessing this larger field could tripple the size of our products > database. (perhaps 3 megs?) > > My question is: > In your opinion should I separate this portion out to a detail.db? > > Our Server has plenty of RAM and is a G4 PPC so I am not sure if there will be > a speed improvment separating them or not. > > Thanks in Advance for your comments. > > > -- Donovan D. Brooke > Systems Administrator/ > Assc. Art Director > Epsen Hillmer Graphics > > > I know I'm making progress when I look at the questions I have > asked in the past and think to myself... how stupid was that > > > ------------------------------------------------------------- > 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/ Pat McCormick

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:

ICVerify problems (2001) [WebDNA] WebDNA installers (2014) Not reading code (1997) remotely add + sign (1997) HomePage Caution (1997) Multiple prices (1997) Adding up weights (1998) Draft Manual, Tutorial, and more (1997) Authenticate (1997) How to redirect based on price subtotal? (1998) Windows 2.1b2 Append Bug? (1997) Return records from another (1997) IE problems persist (2004) Grep Question (2003) NT error logs (1997) ODBC to WebCat (2000) Hiding usernames and passwords in URL (1998) re: Large databases in WebCat (1997) WC2b15 - [HTMLx]...[/HTMLx] problems (1997) more info on [setlineitems] (1997)