Re: What would be sweet is

This WebDNA talk-list message is from

2003

It keeps the original formatting. numero = 54453
interpreted = N
texte = >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/ Associated Messages, from the most recent to the oldest:

Re: What would be sweet is ( Scott Anderson 2003)
Re: What would be sweet is ( Bob Minor 2003)
Re: What would be sweet is ( Jesse Proudman 2003)
Re: What would be sweet is ( Kenneth Grome 2003)
Re: What would be sweet is ( Bob Minor 2003)
Re: What would be sweet is ( Jesse Proudman 2003)
Re: What would be sweet is ( Scott Anderson 2003)
What would be sweet is ( Bob Minor 2003)

>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/ Kenneth Grome

DOWNLOAD WEBDNA NOW!

Re: What would be sweet is

2003

Top Articles:

Related Readings: