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:
newbies to web, spaces in email address (1998)
expansion domain freak out (2003)
Web Developer Product Awards (1997)
Web Merchant process after credit card clears (1998)
"Advanced" Search Algorithm (2008)
Replace and Autonumber (2003)
total number of matches (1999)
Separate SSL Server (1997)
Secure Sever and showcart errors (1997)
Formulas.db + Users.db (1997)
Location of Browser Info.txt file (1997)
contextual shownext (1998)
Bug Report, maybe (1997)
Server IP address? (1998)
Searching Groups for multiple matches (1998)
Browser compatibility (Was: Search Engine bots) (2002)
Major Security Hole IIS NT (1998)
Trouble with Netscape (1998)
typhoon... (1997)
Some Questions (1997)