Re: Updating Prices in Online Database

This WebDNA talk-list message is from

1999


It keeps the original formatting.
numero = 23343
interpreted = N
texte = Thanks, I will give this a try. Gil Poulsen wrote:> Well, yes, it is completely replacing existing records with new ones. I > misunderstood your question. In your case you would want to use the > replace context instead and just specify the key field (in my example, > it is the sku) and the price field. So assuming that both databases have > fields called [price] and [sku], it would look more like this: > > [search db=newrecords.db&neskudatarq=[blank]&max=8000] > > [FoundItems] > > [Replace db=yourdatabase.db&eqskudatarq=[sku]]price=[price][/Replace] > > [/FoundItems] > > [numfound] records have been updated per your request. > > [/search] > > The other fields in the database should remain as they are; at least > they do for me, but if you read the docs it says they will be set to > blank, so maybe PCS can clarify this for us. > Associated Messages, from the most recent to the oldest:

    
  1. Re: Updating Prices in Online Database (Kenneth Grome 1999)
  2. Re: Updating Prices in Online Database (Mike Eberly 1999)
  3. Re: Updating Prices in Online Database (Kenneth Grome 1999)
  4. Re: Updating Prices in Online Database (Gil Poulsen 1999)
  5. Re: Updating Prices in Online Database (Mike Eberly 1999)
  6. Re: Updating Prices in Online Database (Mike Eberly 1999)
  7. Re: Updating Prices in Online Database (Carlos Machado 1999)
  8. Re: Updating Prices in Online Database (PCS Technical Support 1999)
  9. Re: Updating Prices in Online Database (Carlos Machado 1999)
  10. Re: Updating Prices in Online Database (Gil Poulsen 1999)
  11. Re: Updating Prices in Online Database (The Mooseman 1999)
  12. Re: Updating Prices in Online Database (Nitai 1999)
  13. Re: Updating Prices in Online Database (Mike Eberly 1999)
  14. Re: Updating Prices in Online Database (Gil Poulsen 1999)
  15. Updating Prices in Online Database (Mike Eberly 1999)
Thanks, I will give this a try. Gil Poulsen wrote:> Well, yes, it is completely replacing existing records with new ones. I > misunderstood your question. In your case you would want to use the > replace context instead and just specify the key field (in my example, > it is the sku) and the price field. So assuming that both databases have > fields called [price] and [sku], it would look more like this: > > [search db=newrecords.db&neskudatarq=[blank]&max=8000] > > [founditems] > > [Replace db=yourdatabase.db&eqskudatarq=[sku]]price=[price][/Replace] > > [/FoundItems] > > [numfound] records have been updated per your request. > > [/search] > > The other fields in the database should remain as they are; at least > they do for me, but if you read the docs it says they will be set to > blank, so maybe PCS can clarify this for us. > Mike Eberly

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:

Re2: AAgghh!! Help, please. SSL strikes again. (1997) deadlock (2000) writing checkboxes to a database (2000) [OT] Internet connection problem (2003) Client-side Image Maps and WebCat? (1998) Re[3]: 2nd WebCatalog2 Feature Request (1996) Cart # Starting at 1000 (2000) Pithy questions on webcommerce & siteedit (1997) WebCat2 Append problem (B14Macacgi) (1997) Showif Context combined with Search (1997) Problem about [CART] number (1998) Drop Down Menus (2002) Searching multiple fields from one form field (1997) Browser Info.txt (1997) WebCatalog can't find database (1997) Problem (1997) Multiple security dbs (1997) WCf2 and nested tags (1997) Using files in an Email broadcast (1999) Re:listfiles-looking for slick solution (1997)