Multiple price fields
This WebDNA talk-list message is from 2000
It keeps the original formatting.
numero = 32344
interpreted = N
texte = I get a database export from a customer, where are 3 prices for each product:db_prod_id db_price_1 db_price_2 db_price_3 1 10 20 30 2 40 50 60 3 70 80 90No [price] would go to the cart, because there is no such field. I think about two options:1 - I could write a [price] field to a seperate database before each [addlineitem] and [setlineitem], and put this field into the cart: No need to change the original database, but much more database access during work.2 - I could rearrange the database like this: db_prod_id db_group price 1 1 10 1 2 20 1 3 30 2 1 40 2 2 50 2 3 60 3 1 70 3 2 80 3 3 90 This involves a change of the original database but less db access and should be faster, even on Linux. Ok, I loose the ability to use [lookup], but since I can do a case sensitive search for the product ID it shouldn't be slower.The second option is better, right? Peter ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list
. To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/
Associated Messages, from the most recent to the oldest:
| |
- Multiple price fields (Peter Ostry 2000)
|
I get a database export from a customer, where are 3 prices for each product:db_prod_id db_price_1 db_price_2 db_price_3 1 10 20 30 2 40 50 60 3 70 80 90No [price] would go to the cart, because there is no such field. I think about two options:1 - I could write a [price] field to a seperate database before each [addlineitem] and [setlineitem], and put this field into the cart: No need to change the original database, but much more database access during work.2 - I could rearrange the database like this: db_prod_id db_group price 1 1 10 1 2 20 1 3 30 2 1 40 2 2 50 2 3 60 3 1 70 3 2 80 3 3 90 This involves a change of the original database but less db access and should be faster, even on Linux. Ok, I loose the ability to use [lookup], but since I can do a case sensitive search for the product ID it shouldn't be slower.The second option is better, right? Peter ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/
Peter Ostry
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:
do you have a webcatalog tool you want to sell? (1999)
RE: MS Commerce Comparison (long) (1998)
off-topic - printinglib 68K (1997)
Where is f2? (1997)
forming a SKU (1999)
Search 1 Field Twice? (2004)
shipcost (1997)
File Upload (1997)
WebCat2b13MacPlugIn - [shownext method=post] ??? (1997)
[WebDNA] Sorry, WebCatalog server not running. (2008)
WC1.6 to WC2 date formatting (1997)
Firesite cache vs webcat cache (1997)
Letters as SKU (1998)
Tab Charactor (1997)
A national Zip base sales tax db? (1999)
[SHOWIF] (1997)
Interfacing WebMerchant to www.fedex.com (1997)
date tag not interpreted (2000)
emailer (1997)
Running _every_ page through WebCat ? (1997)