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:
hideif/showif causes error if wrapped around searches (2003)
WebCat2 - Getting to the browser's username/password data (1997)
StandardConversions.db (1998)
Showif, Hideif reverse logic ? (1997)
WebCatalog2 Feature Feedback (1996)
Calculating multiple shipping... (1997)
Pre-flight public flag (1997)
Major Security Hole (1998)
Database Fields (1997)
Frames (1997)
different ship dates and shopping carts -- how to? (1997)
emailer (1997)
[SearchString] usage (1997)
OFF TOPIC - sendmail problem (2003)
Sorting search results (1998)
Trouble with carts (2000)
Date Problems (2000)
Redirect me home please? (2000)
Frames and WebCat (1997)
EIMS Problems (1997)