Re: Database Repopulation
This WebDNA talk-list message is from 2004
It keeps the original formatting.
numero = 59563
interpreted = N
texte = 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 adding this to each brand I would then in theory be able to reverse lookup the products in those categories and tag a gender onto them / populate a cross.db. If I was to be honest I would have to own up and say that I have added gender to the base product as I think it can be classed 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 the process of adding products to the products database, I only ever 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 well (as before this was a nightmare). Is this an acceptable use of databases / the right way of doing this? 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 gender 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 fieldname in your products db or a cross db, can not be automated. Unless you already have some sort of way of identifying the product already for being a male/female product!?! > >We have created for such things complete administration templates where our customers could refer to other products or cross referencing their products to many categories in our systems, but still the process can not be automated. > >Nitai > >-- >Redakto - Content Management that simply works >Content Management & eBusiness Systems > >ComputerOil® 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/
Associated Messages, from the most recent to the oldest:
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 adding this to each brand I would then in theory be able to reverse lookup the products in those categories and tag a gender onto them / populate a cross.db. If I was to be honest I would have to own up and say that I have added gender to the base product as I think it can be classed 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 the process of adding products to the products database, I only ever 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 well (as before this was a nightmare). Is this an acceptable use of databases / the right way of doing this? 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 gender 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 fieldname in your products db or a cross db, can not be automated. Unless you already have some sort of way of identifying the product already for being a male/female product!?! > >We have created for such things complete administration templates where our customers could refer to other products or cross referencing their products to many categories in our systems, but still the process can not be automated. > >Nitai > >-- >Redakto - Content Management that simply works >Content Management & eBusiness Systems > >ComputerOil® 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/
Alan White
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:
Cookies and webcat (1997)
Uh...can someone help me out with the b10? (1997)
HELP WITH DATES (1997)
WebCat2 several catalogs? (1997)
Need relative path explanation (1997)
WebCatalog can't find database (1997)
Server slowing down. (1997)
wc 2 pro users - sites, quotes wanted (1997)
encryption seeds xing (1998)
WC allow classified users to edit entry (1999)
Emailer prefs in two places ... (1997)
when is date system date or order date? (1997)
RE: E-mailer error codes (1997)
Threaded Discussion (1998)
triggers (2003)
WebCat2 - Getting to the browser's username/password data (1997)
vs (1997)
Webcat no longer supported? (2006)
Re:Merging databases (1997)
WC2f3 (1997)