Re: autocommit problem

This WebDNA talk-list message is from

1998


It keeps the original formatting.
numero = 19073
interpreted = N
texte = >On a server with WebCat 2.1 and WebStar 3.0, I have > >AutoCommit F > >in the preferences. When I wanted to, I just used a [commitdatabases] >command to write them to disk, which was everytime a database changed. > >Now I want to avoid writing these databases to disk unless I give a >command to do so at my convenience. After I get rid of all the >[commitdatabases], the databases continue to be flushed to disk with each >append or replace. > >This is also true for a new [replace] situation I added (never had a >[commitdabase] context to forget to remove) on a very large database that >I can't spare the time it takes to flush to disk. > >I don't see this behavior on my betastore with demo's of WebCat and >WebStar 2.1 running. Both have the autocommit set to false and always >have. > >Is there another item in my preference folder that could override the >AutoCommit F setting? Is there a conflict with a WebStar 3.0 setting? > >Any clues?[append] automatically writes to disk. It does not need the [commitdatabases] command. So I would assume the autocommit=F would not effect one way or the other this command.regarding the [replace] and it still writing to disk, not to ram and all you did on your templates is edit out [commitdatabase=some.db] and you are on a Mac and webstar you might want to flush the cache via webstar as it might be holding the old copy of the template in ram. and make sure you flush your browser cache also. Sometimes such minor changes and or changes made seconds apart the older template is the one you see not the newer one so your changes do not show up.=============================================== Gary Richter PanaVise Products, Inc. 7540 Colbert Dr. Reno, Nevada 89511 Ph: 702.850.2900 Fx: 702.850.2929 Email: grichter@panavise.com http://www.panavise.com =============================================== Associated Messages, from the most recent to the oldest:

    
  1. Re: autocommit problem (Angel Bennett 1998)
  2. Re: autocommit problem (Angel Bennett 1998)
  3. Re: autocommit problem (Angel Bennett 1998)
  4. Re: autocommit problem (Angel Bennett 1998)
  5. Re: autocommit problem (Kenneth Grome 1998)
  6. Re: autocommit problem (PCS Technical Support 1998)
  7. Re: autocommit problem (Kenneth Grome 1998)
  8. Re: autocommit problem (Sandra L. Pitner 1998)
  9. Re: autocommit problem (Sandra L. Pitner 1998)
  10. Re: autocommit problem (Peter Ostry 1998)
  11. Re: autocommit problem (PCS Technical Support 1998)
  12. Re: autocommit problem (Sandra L. Pitner 1998)
  13. Re: autocommit problem (Kenneth Grome 1998)
  14. Re: autocommit problem (PCS Technical Support 1998)
  15. Re: autocommit problem (Gary Richter 1998)
  16. Re: autocommit problem (Sandra L. Pitner 1998)
  17. autocommit problem (Sandra L. Pitner 1998)
>On a server with WebCat 2.1 and WebStar 3.0, I have > >AutoCommit F > >in the preferences. When I wanted to, I just used a [commitdatabases] >command to write them to disk, which was everytime a database changed. > >Now I want to avoid writing these databases to disk unless I give a >command to do so at my convenience. After I get rid of all the >[commitdatabases], the databases continue to be flushed to disk with each >append or replace. > >This is also true for a new [replace] situation I added (never had a >[commitdabase] context to forget to remove) on a very large database that >I can't spare the time it takes to flush to disk. > >I don't see this behavior on my betastore with demo's of WebCat and >WebStar 2.1 running. Both have the autocommit set to false and always >have. > >Is there another item in my preference folder that could override the >AutoCommit F setting? Is there a conflict with a WebStar 3.0 setting? > >Any clues?[append] automatically writes to disk. It does not need the [commitdatabases] command. So I would assume the autocommit=F would not effect one way or the other this command.regarding the [replace] and it still writing to disk, not to ram and all you did on your templates is edit out [commitdatabase=some.db] and you are on a Mac and webstar you might want to flush the cache via webstar as it might be holding the old copy of the template in ram. and make sure you flush your browser cache also. Sometimes such minor changes and or changes made seconds apart the older template is the one you see not the newer one so your changes do not show up.=============================================== Gary Richter PanaVise Products, Inc. 7540 Colbert Dr. Reno, Nevada 89511 Ph: 702.850.2900 Fx: 702.850.2929 Email: grichter@panavise.com http://www.panavise.com =============================================== Gary Richter

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:

WebCat2 Append problem (B14Macacgi) (1997) Getting total number of items ordered (1997) Upgrading to 4.0 (2000) redirect not passing vars (2004) [WebDNA] [OT] hello (2012) db protection on NT (1997) GoLive CyberStudio 1.0.1 (1997) Plugin or CGI or both (1997) ACGI processing for .html (1997) Initiating NewCart (1997) 3 card formulas! (1999) Hiding Email Addresses (2003) Payfuse? (2006) HomePage Caution (1997) [WebDNA] help with writefile (2012) success - serial numbers and webmerch (1997) syntax question, not in online refernce (1997) Still search problems! (1999) problems with 2 tags (1997) Web Catalog 2 demo (1997)