Re: What would be sweet is

This WebDNA talk-list message is from

2003


It keeps the original formatting.
numero = 54451
interpreted = N
texte = On Nov 25, 2003, at 4:14 PM, Scott Anderson wrote: > 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. > > Each store would have its own SQL conf file for SQL settings; host, > username, password, database, etc... Or perhaps just a reference to a > WebDNA > global registered SQL database, that is automatically 'mounted' when > WebDNA > starts up. > > The goal being that no template changes would be required to switch to > SQL > for the ecommerce stuff. That would be incredible. Imagine the load a pair of G5s running WebDNA to a SQL backend could take. -- Jesse Williams-Proudman Blue Box Development :: Custom Web Solutions +1.206.778.8777 :: jesse@blueboxdev.com *Happy Holidays* ------------------------------------------------------------- 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)
On Nov 25, 2003, at 4:14 PM, Scott Anderson wrote: > 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. > > Each store would have its own SQL conf file for SQL settings; host, > username, password, database, etc... Or perhaps just a reference to a > WebDNA > global registered SQL database, that is automatically 'mounted' when > WebDNA > starts up. > > The goal being that no template changes would be required to switch to > SQL > for the ecommerce stuff. That would be incredible. Imagine the load a pair of G5s running WebDNA to a SQL backend could take. -- Jesse Williams-Proudman Blue Box Development :: Custom Web Solutions +1.206.778.8777 :: jesse@blueboxdev.com *Happy Holidays* ------------------------------------------------------------- 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/ Jesse Proudman

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:

Thread (1999) Help! WebCat2 bug (1997) [Shell] help with Tarring files (2002) Only charge card when product shipped ? (1997) if/then/else question - nevermind, my stupidity... (2000) OT: Amazon Patents (2000) Multiple catalog databases and showcart (1997) Generating Report Totals (1997) Re:Dumb Question about Docs (1997) Chatroom (2000) Special characters in field names (1998) Where is f2? (1997) Line items in table cells (1997) Not really WebCat (1997) Can't test the beta (2000) blank page from template (1997) [OT] MACWORLD (2003) Big Databases (1997) For those of you not on the WebCatalog Beta... (1997) RAM variables (1997)