Re: What would be sweet is

This WebDNA talk-list message is from

2003


It keeps the original formatting.
numero = 54456
interpreted = N
texte = Relax, Ken. This only effects the ecommerce stuff, and I guess you missed the 'sandbox' note. This setting would be maintained at the Sandbox level, so it would be easy to have one store use the SQL for ecommerce, and another store use the native WebDNA ecommerce code. -----Original Message----- From: Kenneth Grome [mailto:kengrome@webdna.net] Sent: Tuesday, November 25, 2003 4:28 PM To: WebDNA Talk Subject: Re: What would be sweet is >Actually, what I have been considering is a new WebDNA admin pref that reads >something like: > >eCommerce use SQL TRUE/FALSE > >If set to true, all existing WebDNA ecommerce tags and contexts (including >[cart]) would use a SQL database (using our new native SQL code). Each >sandbox would have its own setting. This is NOT a good idea ... because then we would lose the current flexibility of being able to use either native or sql db's as required (or as desired) ... :( I (for one) do NOT want to be forced into using all sql db's just because I might need to use ONE in a web site, but the pref you're suggesting would FORCE ME to do it this way. Please think about the consequences of forcing all webdna db's in a particular site to be either SQL or non-SQL! I'm sure the reason why others have suggested having a "sql" parameter in the tag is precisely to allow them to continue using non-sql db's as well as sql db's in the same template, or even in the same web site for that matter ... -- Sincerely, Kenneth Grome ------------------------------------------------------------- Outsource your WebDNA programming for $18 an hour or less! ------------------------------------------------------------- ------------------------------------------------------------- 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://webdna.smithmicro.com/ ------------------------------------------------------------- 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://webdna.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Re: What would be sweet is ( Scott Anderson 2003)
  2. Re: What would be sweet is ( Bob Minor 2003)
  3. Re: What would be sweet is ( Jesse Proudman 2003)
  4. Re: What would be sweet is ( Kenneth Grome 2003)
  5. Re: What would be sweet is ( Bob Minor 2003)
  6. Re: What would be sweet is ( Jesse Proudman 2003)
  7. Re: What would be sweet is ( Scott Anderson 2003)
  8. What would be sweet is ( Bob Minor 2003)
Relax, Ken. This only effects the ecommerce stuff, and I guess you missed the 'sandbox' note. This setting would be maintained at the Sandbox level, so it would be easy to have one store use the SQL for ecommerce, and another store use the native WebDNA ecommerce code. -----Original Message----- From: Kenneth Grome [mailto:kengrome@webdna.net] Sent: Tuesday, November 25, 2003 4:28 PM To: WebDNA Talk Subject: Re: What would be sweet is >Actually, what I have been considering is a new WebDNA admin pref that reads >something like: > >eCommerce use SQL TRUE/FALSE > >If set to true, all existing WebDNA ecommerce tags and contexts (including >[cart]) would use a SQL database (using our new native SQL code). Each >sandbox would have its own setting. This is NOT a good idea ... because then we would lose the current flexibility of being able to use either native or sql db's as required (or as desired) ... :( I (for one) do NOT want to be forced into using all sql db's just because I might need to use ONE in a web site, but the pref you're suggesting would FORCE ME to do it this way. Please think about the consequences of forcing all webdna db's in a particular site to be either SQL or non-SQL! I'm sure the reason why others have suggested having a "sql" parameter in the tag is precisely to allow them to continue using non-sql db's as well as sql db's in the same template, or even in the same web site for that matter ... -- Sincerely, Kenneth Grome ------------------------------------------------------------- Outsource your WebDNA programming for $18 an hour or less! ------------------------------------------------------------- ------------------------------------------------------------- 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://webdna.smithmicro.com/ ------------------------------------------------------------- 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://webdna.smithmicro.com/ Scott Anderson

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:

carriage returns in data (1997) Press Release hit the NewsWire!!! (1997) HELLO (2000) Append command (2000) problems with 2 tags (1997) can we get string variables? (1998) webcat2b12 CGI -- Date comparisons (1997) error: Too many nested [xxx] contexts (1997) Hard Questions ? (1997) Mozilla/4. and Browser Info.txt (1997) [max] always equals 0 in search context (2000) High ASCII inside [LOOKUP] inside [LISTWORDS] (1998) all records returned. (1997) [OT] Internet Access (2003) PCS Frames (1997) Date search - yes or no (1997) New Mac Public Beta Available (1997) Template Encryption (1998) Re:no [search] with NT (1997) Emailer problems. (1998)