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:
[BULK] [WebDNA] A new commerce system for v7+ (2011)
This message couldn't reach the list! (multi-column (1998)
SSL problems (2002)
Change in Host? (1999)
Comments in db? (1997)
WebCat2b15MacPlugIn - [authenticate] not [protect] (1997)
Quickie question on the email templates (1997)
[/application] error? (1997)
how would you trigger something to happen once a week - every (2001)
TRAINING videos - Prove IT. (1998)
i'm dumb today (2004)
tiny Linux issue (1999)
Possible Hijacking from Globix (2002)
Grepping URL-Encoded Text (2004)
Append..... doesn't (2000)
Re:HTTP header line is too long? (1997)
Max Record length restated as maybe bug (1997)
Deleting Orders (1997)
WebCat2b13MacPlugIn - more [date] problems (1997)
[WebDNA] OT - some girls like guys for their WebDNA (2010)