Re: multiple product databases

This WebDNA talk-list message is from

1997

It keeps the original formatting. numero = 15861
interpreted = N
texte = >Yes, I'm wanting to break out the databases of my store into two or actually>three. This way each catagory of Multiple categories of products could be>maintained seperately.>>The nested price lookup will solve one of my problems, the others have to do>with adding, removing and showing cart items due to the value of db= needing>to be passed through in the url.The required db just makes some things simpler for most people, because it helps default quite a few values. For instance, putting [customfield] inside a [LineItems] context will automatically do the lookup (based on SKU) for that product and return the proper text from the database. Also, the default price formula automatically looks up the price in whatever db is specified at the time of $Add or [AddLineItem].You can get away with not using the single db, but you must make your formulas smart enough to know where to look up the information. I recomend for simplicity that if you really want separate databases, you should administer them separately, but then combine them into a single database for final 'publication'. This combining can happen automatically in some kind of administrative template you create. We do this on some of our hosted sites so vendors can upload 'change lists' and our WebDNA blends the new with the old database.Grant Hulbert, V.P. Engineering | ==== eCommerce for the Rest of Us ====Pacific Coast Software | WebCatalog, WebMerchant,11770 Bernardo Plaza Court | SiteEdit Pro, PhotoMaster,San Diego, CA 92128 | Typhoon619/675-1106 Fax: 619/675-0372 | http://www.smithmicro.com/ Associated Messages, from the most recent to the oldest:

Re: multiple product databases (Grant Hulbert 1997)
Re: multiple product databases (Ray Hatch 1997)
Re: multiple product databases (Grant Hulbert 1997)
Re: multiple product databases (Kenneth Grome 1997)
multiple product databases (Ray Hatch 1997)

>Yes, I'm wanting to break out the databases of my store into two or actually>three. This way each catagory of Multiple categories of products could be>maintained seperately.>>The nested price lookup will solve one of my problems, the others have to do>with adding, removing and showing cart items due to the value of db= needing>to be passed through in the url.The required db just makes some things simpler for most people, because it helps default quite a few values. For instance, putting [customfield] inside a [lineitems] context will automatically do the lookup (based on SKU) for that product and return the proper text from the database. Also, the default price formula automatically looks up the price in whatever db is specified at the time of $Add or [addlineitem].You can get away with not using the single db, but you must make your formulas smart enough to know where to look up the information. I recomend for simplicity that if you really want separate databases, you should administer them separately, but then combine them into a single database for final 'publication'. This combining can happen automatically in some kind of administrative template you create. We do this on some of our hosted sites so vendors can upload 'change lists' and our WebDNA blends the new with the old database.Grant Hulbert, V.P. Engineering | ==== eCommerce for the Rest of Us ====Pacific Coast Software | WebCatalog, WebMerchant,11770 Bernardo Plaza Court | SiteEdit Pro, PhotoMaster,San Diego, CA 92128 | Typhoon619/675-1106 Fax: 619/675-0372 | http://www.smithmicro.com/ Grant Hulbert

DOWNLOAD WEBDNA NOW!

Re: multiple product databases

1997

Top Articles:

Related Readings: