Re: Editing only the price field in the database
This WebDNA talk-list message is from 1998
It keeps the original formatting.
numero = 21657
interpreted = N
texte = >Basically, I would like to be able to export everything from our >off-line database, create a temporary online database with the >exported info, be able to compare the part numbers in the temporary >database with the part numbers in the Catalog.db and when it finds >matching part numbers, replace the price field in the Catalog.db with >the price in the temporary database. Is it possible to do this using >WebCat?Yes, you can certainly write some 'merge' WebDNA that searches thru an update database and does a [replace] on your main database with the new price information. It can take some time for large databases, though.But I'd recommend a nice little hybrid instead: keep the price information *out* of your main Catalog.db, and instead keep a separate SKU/price database which contains just those two fields. That way you can easily export just those 2 fields from your offline database, and whenever you need to find the price of something in your templates, just do a quick [lookup] in the price database to see its current value. You can even modify your Formulas.db to automatically pull prices from this alternate database.Technical Support | ==== eCommerce and Beyond ==== Pacific Coast Software | WebCatalog, WebMerchant, 11770 Bernardo Plaza Court | SiteEdit Pro, PhotoMaster, San Diego, CA 92128 | Typhoon 619/675-1106 Fax: 619/675-0372 | http://www.smithmicro.com/
Associated Messages, from the most recent to the oldest:
>Basically, I would like to be able to export everything from our >off-line database, create a temporary online database with the >exported info, be able to compare the part numbers in the temporary >database with the part numbers in the Catalog.db and when it finds >matching part numbers, replace the price field in the Catalog.db with >the price in the temporary database. Is it possible to do this using >WebCat?Yes, you can certainly write some 'merge' WebDNA that searches thru an update database and does a
[replace] on your main database with the new price information. It can take some time for large databases, though.But I'd recommend a nice little hybrid instead: keep the price information *out* of your main Catalog.db, and instead keep a separate SKU/price database which contains just those two fields. That way you can easily export just those 2 fields from your offline database, and whenever you need to find the price of something in your templates, just do a quick
[lookup] in the price database to see its current value. You can even modify your
formulas.db to automatically pull prices from this alternate database.Technical Support | ==== eCommerce and Beyond ==== Pacific Coast Software | WebCatalog, WebMerchant, 11770 Bernardo Plaza Court | SiteEdit Pro, PhotoMaster, San Diego, CA 92128 | Typhoon 619/675-1106 Fax: 619/675-0372 | http://www.smithmicro.com/
PCS Technical Support
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:
Country & Ship-to address & other fields ? (1997)
[WebDNA] Successful, working WebDNA7/CentOS install? (2013)
Multiple prices (1997)
Pager notification of completed orders (1998)
Forms Search Questions (1997)
DataBaseHelper Flawed (1997)
can WC render sites out? (1997)
Which beta for w* 4.1 and a problem w/b12 (1999)
Date problems-more (1997)
RE: [WebDNA] Good advise on [Showif] or alternative... (2012)
Security hole in WebCat? (1999)
European Dates (1998)
[format 40s]text[/format] doesn't work (1997)
Comments in db? (1997)
Search returns all, not 20 (1997)
Sending Email (2004)
Payment calculator ?? (2000)
[WebDNA] Different results for [THISURL] (2018)
docs for WebCatalog2 (1997)
simple answer? [hideif] (1997)