Re: Database Repopulation
This WebDNA talk-list message is from 2004
It keeps the original formatting.
numero = 59553
interpreted = N
texte = Hello again... At the moment I currently have 2 databases containing product specific data, I have one that holds product specific data (what we have called a base product) and then I have a products database that holds the stock for these products. The products database reads info from the base products when it is being populated (descriptions etc) and then colour size variations are entered only into the products database... The easiest place for me to tag any product specific information is going to be in a base product (as it will update the product variations in the products database), in doing this am I not in effect creating the equivelant of the cross.db without having to integrate a whole new db (and associated links)? Also I have just confirmed inhouse that a mens and womens Dunk Hi (for example) would have different base product ID's, this has been done so that we can have the base products pointing at the different brands which I now need to bring together. From ID Product Brand 1 Dunk Hi Nike 2 Dunk Hi Nike Womens To ID Product Brand Gender 1 Dunk Hi Nike m 2 Dunk Hi Nike f I can then search the products database for neBranddatarq=find_all&eqGenderdatarq=m Hmmm.... I dunno if I am just going round in circles for no good reason... I think I can see the answer above but we have approximately 1300 base products & 8000 products (variations) in our products database so that is 1300 times I am going to have to go into a product, change brand, add a gender and submit the change. Seems like an awful lot of manual work... Geez... time for some coffee and move on me thinks... I can facilitate the change I am talking about above no problem but it gets messy the minute I start to move products around brands... that is why I talked about using a gender handle on a brand to look up base products (pointing that brand) and add a gender and then run another script to move products from one brand to another... never done anything like that yet and 8000 products is a lot to screw up and making dupilcate / test db's to play with and then switching over could get well confusing... Thanks for your input I'm off to put on coffee... I hope I am making sense... Alan Nitai @ ComputerOil wrote: >Alan > >I can understand what the problem is, but as I have mentioned you are really better off with a cross database (I wrote "tables" but what I meant was a database). > >Example: > >Your db now (I added a ID): > >205 Dunk Hi Footwear Nike >206 Dunk Hi Footwear Nike Womens >207 History Books Nike Books > >Now we create a category table: > >1 men >2 girls > >Now create another "crossdb" which holds the category and the product id: > >1 205 > >This would mean that the product with the ID 205 is in the category 1 (men). You will create a record for each id/relationship. So if all of the sudden the product 205 should also appear in girls then you will have this: > >1 205 >2 205 > >Hope this helps. > >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: Thursday, October 07, 2004 3:16 PM >To: WebDNA Talk >Subject: Re: Database Repopulation > > >Hi Nitai > >Unfortunately I am still on Version 4.5.1 so I cannot use tables and >even if I was to upgrade I would need to learn how to use the new >features available to me such as tables before using them. Categories >are not actually a problem at the moment, it is more how I negotiate >imalgimating brands where I am getting a little confused. > >I want to change from something like > >Dunk Hi Footwear Nike >Dunk Hi Footwear Nike Womens >History Books Nike Books > >To > >Dunk Hi Footwear Nike m >Dunk Hi Footwear Nike f >History Books Nike u > >In order to do this I need to change my products to contain a gender >flag and also point them to a single brand, my problem lies where I have >a cross over... do I move all of my womens products into mens (notice >in the example above only womens is specified) first and give them a >gender flag... once I have moved all products into individual brands, I >can then break them up by use of the flags in brand menu's ie (taken >from above) :- > >Mens Brands >Nike >Womens Brands >Nike >Toys & Accessories >Nike > >Each of the links above would lead to a set of category sub navigation. > >Hope that makes it a little clearer... I guess I am just fishing to see >if I am on the right track or if there is a better quicker way to do it >like writing a script to strip out values and populate db's for me... > >For example: Before going down this route I decided to try and attach >gender to brands as a quick route of acomplishing what is required, in >hindsight I noticed inherrint problems with doing it like this but I >actually now have a *handle* I could use to flag all my products in each >brand with either an m for male brands or f for female brands... (I >think I may have a few hurdles still doing it that way) > >Anyway, I hope what I am trying to do is a little clearer for anyone >following this and thanks for your suggestion. > >Regards >Alan > > > >Nitai @ ComputerOil wrote: > > > >>Hi Alan, >> >>I would create a "super" Table with the Men and Girls category. Then add a crosstable which will only hold the ID of the Men/Girl Category and the ID of the product. >> >>Like this you can add many more categories (if your boss would need more) and you will also not touch the products db and you can add an unlimited number of entries and cross entries. >> >>Just a quick thought at the top of my head........ >> >>Nitai >> >> >> >> >> > > >------------------------------------------------------------- >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:
Hello again... At the moment I currently have 2 databases containing product specific data, I have one that holds product specific data (what we have called a base product) and then I have a products database that holds the stock for these products. The products database reads info from the base products when it is being populated (descriptions etc) and then colour size variations are entered only into the products database... The easiest place for me to tag any product specific information is going to be in a base product (as it will update the product variations in the products database), in doing this am I not in effect creating the equivelant of the cross.db without having to integrate a whole new db (and associated links)? Also I have just confirmed inhouse that a mens and womens Dunk Hi (for example) would have different base product ID's, this has been done so that we can have the base products pointing at the different brands which I now need to bring together. From ID Product Brand 1 Dunk Hi Nike 2 Dunk Hi Nike Womens To ID Product Brand Gender 1 Dunk Hi Nike m 2 Dunk Hi Nike f I can then search the products database for neBranddatarq=find_all&eqGenderdatarq=m Hmmm.... I dunno if I am just going round in circles for no good reason... I think I can see the answer above but we have approximately 1300 base products & 8000 products (variations) in our products database so that is 1300 times I am going to have to go into a product, change brand, add a gender and submit the change. Seems like an awful lot of manual work... Geez... time for some coffee and move on me thinks... I can facilitate the change I am talking about above no problem but it gets messy the minute I start to move products around brands... that is why I talked about using a gender handle on a brand to look up base products (pointing that brand) and add a gender and then run another script to move products from one brand to another... never done anything like that yet and 8000 products is a lot to screw up and making dupilcate / test db's to play with and then switching over could get well confusing... Thanks for your input I'm off to put on coffee... I hope I am making sense... Alan Nitai @ ComputerOil wrote: >Alan > >I can understand what the problem is, but as I have mentioned you are really better off with a cross database (I wrote "tables" but what I meant was a database). > >Example: > >Your db now (I added a ID): > >205 Dunk Hi Footwear Nike >206 Dunk Hi Footwear Nike Womens >207 History Books Nike Books > >Now we create a category table: > >1 men >2 girls > >Now create another "crossdb" which holds the category and the product id: > >1 205 > >This would mean that the product with the ID 205 is in the category 1 (men). You will create a record for each id/relationship. So if all of the sudden the product 205 should also appear in girls then you will have this: > >1 205 >2 205 > >Hope this helps. > >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: Thursday, October 07, 2004 3:16 PM >To: WebDNA Talk >Subject: Re: Database Repopulation > > >Hi Nitai > >Unfortunately I am still on Version 4.5.1 so I cannot use tables and >even if I was to upgrade I would need to learn how to use the new >features available to me such as tables before using them. Categories >are not actually a problem at the moment, it is more how I negotiate >imalgimating brands where I am getting a little confused. > >I want to change from something like > >Dunk Hi Footwear Nike >Dunk Hi Footwear Nike Womens >History Books Nike Books > >To > >Dunk Hi Footwear Nike m >Dunk Hi Footwear Nike f >History Books Nike u > >In order to do this I need to change my products to contain a gender >flag and also point them to a single brand, my problem lies where I have >a cross over... do I move all of my womens products into mens (notice >in the example above only womens is specified) first and give them a >gender flag... once I have moved all products into individual brands, I >can then break them up by use of the flags in brand menu's ie (taken >from above) :- > >Mens Brands >Nike >Womens Brands >Nike >Toys & Accessories >Nike > >Each of the links above would lead to a set of category sub navigation. > >Hope that makes it a little clearer... I guess I am just fishing to see >if I am on the right track or if there is a better quicker way to do it >like writing a script to strip out values and populate db's for me... > >For example: Before going down this route I decided to try and attach >gender to brands as a quick route of acomplishing what is required, in >hindsight I noticed inherrint problems with doing it like this but I >actually now have a *handle* I could use to flag all my products in each >brand with either an m for male brands or f for female brands... (I >think I may have a few hurdles still doing it that way) > >Anyway, I hope what I am trying to do is a little clearer for anyone >following this and thanks for your suggestion. > >Regards >Alan > > > >Nitai @ ComputerOil wrote: > > > >>Hi Alan, >> >>I would create a "super" Table with the Men and Girls category. Then add a crosstable which will only hold the ID of the Men/Girl Category and the ID of the product. >> >>Like this you can add many more categories (if your boss would need more) and you will also not touch the products db and you can add an unlimited number of entries and cross entries. >> >>Just a quick thought at the top of my head........ >> >>Nitai >> >> >> >> >> > > >------------------------------------------------------------- >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:
Conveting Characters to Graphics (1997)
Showif ~ Netscape : Showif ~ MSIE (2001)
Multiple prices (1997)
Multiple Passwords (1997)
Search/sort in URL Was: GuestBook example (1997)
Web Catalog 2 demo (1997)
PCS Frames (1997)
Question about links (1999)
[ConvertChars] problem (1997)
RE: Upload (1998)
Search on encrypted field (2000)
quantity minimum problem (1997)
shopcost, unitshipcost (2002)
For those of you not on the WebCatalog Beta... (1997)
WebMerchant Mac 3.0 beta available (1998)
WCS Newbie question (1997)
WebCatalog and Bar Code Scanners (1999)
multiple search commands (1997)
Shopping problems with 2.1b3 acgi (1997)
Generating Options for a Form. (1997)