Re: Database Repopulation

This WebDNA talk-list message is from

2004


It keeps the original formatting.
numero = 59564
interpreted = N
texte = Good Afternoon Alan (from my part of the world) :-) I don=E2=80=99t feel insulted or anything alike if you do it your= way :-)))) I have done for years with databases what you are doing, but afte= r some time of building tones of solutions and afterwards adding=20= or removing records I have come to start using cross dbs. But as I said, do what works the best way for you. I myself tend=20= to always do more work upfront, but then I don=E2=80=99t have to=20= rework later on! Have a nice morning. Nitai -- Redakto - Content Management that simply works Content Management & eBusiness Systems ComputerOil=C2=AE AG Dammstrasse 7 5400 Baden / Switzerland Telefon +41 (0)844 44 55 66 info@computeroil.com http://computeroil.com -----Original Message----- From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com] On Beh= alf Of Alan White Sent: Friday, October 08, 2004 11:47 AM To: WebDNA Talk Subject: Re: Database Repopulation Good morning Nitai. I think I can maybe be sneaky and attach gender to brands first (= seeing as I built it before going down the gender on item route) but by=20= adding this to each brand I would then in theory be able to reverse look= up the products in those categories and tag a gender onto them / populat= e a cross.db. If I was to be honest I would have to own up and say t= hat I have added gender to the base product as I think it can be classe= d as specific to a product (ie the same for all colour size variations= ). I tested it and it seems to have worked but I am unsure as to how normalised this is? The reason I made this base products database was to normalise th= e process of adding products to the products database, I only ever=20= enter descriptions, price, (and now gender too) product title etc once= and I may have 20 variations of a product so this method works very wel= l (as before this was a nightmare). Is this an acceptable use of databases / the right way of doing t= his? I dont want to sound like I am ignoring your advice about the cross= ..db by the way, this just seems like the most logical place to put gende= r i.e. at the point where I am adding a product. I look forward to your reply. Regards Alan Nitai @ ComputerOil wrote: >That process, the one of filling the data, may it be an extra fi= eldname in your products db or a cross db, can not be automated.=20= Unless you already have some sort of way of identifying the produ= ct already for being a male/female product!?! > >We have created for such things complete administration template= s where our customers could refer to other products or cross refe= rencing their products to many categories in our systems, but sti= ll the process can not be automated. > >Nitai > >-- >Redakto - Content Management that simply works >Content Management & eBusiness Systems > >ComputerOil=C2=AE AG >Dammstrasse 7 >5400 Baden / Switzerland >Telefon +41 (0)844 44 55 66 > >info@computeroil.com >http://computeroil.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/ ------------------------------------------------------------- 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:

    
  1. Re: Database Repopulation ( Alan White 2004)
  2. Re: Database Repopulation ( "Nitai @ ComputerOil" 2004)
  3. Re: Database Repopulation ( Alan White 2004)
  4. Re: Database Repopulation ( Donovan Brooke 2004)
  5. Re: Database Repopulation ( Alan White 2004)
  6. Re: Database Repopulation ( Donovan Brooke 2004)
  7. Re: Database Repopulation ( Alan White 2004)
  8. Re: Database Repopulation ( "Nitai @ ComputerOil" 2004)
  9. Re: Database Repopulation ( Gary Krockover 2004)
  10. Re: Database Repopulation ( Alan White 2004)
  11. Re: Database Repopulation ( Alan White 2004)
  12. Re: Database Repopulation ( "Nitai @ ComputerOil" 2004)
  13. Database Repopulation ( Alan White 2004)
Good Afternoon Alan (from my part of the world) :-) I don=E2=80=99t feel insulted or anything alike if you do it your= way :-)))) I have done for years with databases what you are doing, but afte= r some time of building tones of solutions and afterwards adding=20= or removing records I have come to start using cross dbs. But as I said, do what works the best way for you. I myself tend=20= to always do more work upfront, but then I don=E2=80=99t have to=20= rework later on! Have a nice morning. Nitai -- Redakto - Content Management that simply works Content Management & eBusiness Systems ComputerOil=C2=AE AG Dammstrasse 7 5400 Baden / Switzerland Telefon +41 (0)844 44 55 66 info@computeroil.com http://computeroil.com -----Original Message----- From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com] On Beh= alf Of Alan White Sent: Friday, October 08, 2004 11:47 AM To: WebDNA Talk Subject: Re: Database Repopulation Good morning Nitai. I think I can maybe be sneaky and attach gender to brands first (= seeing as I built it before going down the gender on item route) but by=20= adding this to each brand I would then in theory be able to reverse look= up the products in those categories and tag a gender onto them / populat= e a cross.db. If I was to be honest I would have to own up and say t= hat I have added gender to the base product as I think it can be classe= d as specific to a product (ie the same for all colour size variations= ). I tested it and it seems to have worked but I am unsure as to how normalised this is? The reason I made this base products database was to normalise th= e process of adding products to the products database, I only ever=20= enter descriptions, price, (and now gender too) product title etc once= and I may have 20 variations of a product so this method works very wel= l (as before this was a nightmare). Is this an acceptable use of databases / the right way of doing t= his? I dont want to sound like I am ignoring your advice about the cross= ..db by the way, this just seems like the most logical place to put gende= r i.e. at the point where I am adding a product. I look forward to your reply. Regards Alan Nitai @ ComputerOil wrote: >That process, the one of filling the data, may it be an extra fi= eldname in your products db or a cross db, can not be automated.=20= Unless you already have some sort of way of identifying the produ= ct already for being a male/female product!?! > >We have created for such things complete administration template= s where our customers could refer to other products or cross refe= rencing their products to many categories in our systems, but sti= ll the process can not be automated. > >Nitai > >-- >Redakto - Content Management that simply works >Content Management & eBusiness Systems > >ComputerOil=C2=AE AG >Dammstrasse 7 >5400 Baden / Switzerland >Telefon +41 (0)844 44 55 66 > >info@computeroil.com >http://computeroil.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/ ------------------------------------------------------------- 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/ "Nitai @ ComputerOil"

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:

RE: formula.db, adding option prices (1997) Macos8.6 to X migration problems (2000) Great product and great job ! (1997) input problem (1999) Order not created error (1997) Strange intermittent WebDNA problems (2008) Bizarre behavior texta behavior (2004) [date format] w/in sendmail (1997) Where can I get 'ssh'? (was: WebCatalog on Linux/MacOSX/etc) (2000) File Upload and Platform (2001) WebMerchant 2.1.2 (1998) Separate SSL Server (1997) WebCatalog Use Question (1997) Forbidden CGI Error (1997) Database (1999) WCS Newbie question (1997) Customer login feature (2004) WebCommerce: Folder organization ? (1997) Where is the bug fix info for 4.0.1? (2000) OT: javascript help (2003)