Re: Database Repopulation
This WebDNA talk-list message is from 2004
It keeps the original formatting.
numero = 59565
interpreted = N
texte = Hi I think the thing with this is that the site is never going to not need this piece of information and I think I have put it in the correct place... I fully understand what you are saying about more work upfront means less later on and I have done my best to put this info where it will hopefully never change... A girls bag should always belong to girls unless you are a transvestite ;-) Thanks for all of your advice. Alan Nitai @ ComputerOil wrote: >Good Afternoon Alan (from my part of the world) :-) > >I don’t feel insulted or anything alike if you do it your way :-)))) > >I have done for years with databases what you are doing, but after some time of building tones of solutions and afterwards adding 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 to always do more work upfront, but then I don’t have to rework later on! > >Have a nice morning. > >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 > >-----Original Message----- >From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com] On Behalf 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 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/ > > > >------------------------------------------------------------- >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:
Hi I think the thing with this is that the site is never going to not need this piece of information and I think I have put it in the correct place... I fully understand what you are saying about more work upfront means less later on and I have done my best to put this info where it will hopefully never change... A girls bag should always belong to girls unless you are a transvestite ;-) Thanks for all of your advice. Alan Nitai @ ComputerOil wrote: >Good Afternoon Alan (from my part of the world) :-) > >I don’t feel insulted or anything alike if you do it your way :-)))) > >I have done for years with databases what you are doing, but after some time of building tones of solutions and afterwards adding 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 to always do more work upfront, but then I don’t have to rework later on! > >Have a nice morning. > >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 > >-----Original Message----- >From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com] On Behalf 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 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/ > > > >------------------------------------------------------------- >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/
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:
possible, WebCat2.0 and checkboxes-restated (1997)
Purchased cart being overwritten - still !?? (1997)
One more try (1997)
WebSiphon and MGI links (2000)
New command suggestion (was Modifying databasesmanually) (1997)
Displaying photo attached to first record (1997)
TCPConnect misbehavin' for me. (2000)
PCS Frames (1997)
Help name our technology! I found it (1997)
Emailer help....! (1997)
can WC render sites out? (1997)
Date search - yes or no (1997)
Templates for Customer Database? (1997)
Normalizing Dates and Phone numbers (2000)
[math] variable question (1997)
My slower response (1997)
Database Field Additions (2000)
WebCat Refrence problem (2000)
Sorting error (1997)
Dumb Question about Docs (1997)