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:

Changes to the List (1997) Strange intermittent WebDNA problems (2008) Trouble changing a variable. (2000) invoice.tpl (1998) 2.0 Info (1997) eBay API thru webDNA (2004) form data submission gets truncated (1997) WebStar and CopyFile (2000) RE: [WebDNA] WebSite Examples (2008) Was AJAX, Now JS, XML, CSS LISTS (2006) View order not right (1997) Price recalc based on quantity (1997) Weird error/limit - something amiss? (1997) RequiredFields template (1997) Return records from another (1997) using a link like http://www.domain.com/username (2000) [input]?? (1998) A better WebCat whois (was [OT] Domain Name Scam) (2000) [search][founditems][orderfile] (2003) Size limit for tmpl editor ? (1997)