Re: autocommit problem

This WebDNA talk-list message is from

1998


It keeps the original formatting.
numero = 19081
interpreted = N
texte = >Replace writes to disk every few hundred or so operations, for internal >reasons. This probably explains what I'm seeing and why what I want to do won't work. It's a huge file (100 Megs) and the last thing I want is for it to be written to disk often. And every few hundred or so operations is a tad too frequent for this purpose on a live server (and explains why I don't see it on low traffic beta site). Is it just writing the changes or flushing the whole darn database?Is there a way to prevent this writing to disk besides autocommit off, which only works to a limited degree? If not, my next post will probably be about how to do what I'm trying to do! ;-)ThanksSandy 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)
>Replace writes to disk every few hundred or so operations, for internal >reasons. This probably explains what I'm seeing and why what I want to do won't work. It's a huge file (100 Megs) and the last thing I want is for it to be written to disk often. And every few hundred or so operations is a tad too frequent for this purpose on a live server (and explains why I don't see it on low traffic beta site). Is it just writing the changes or flushing the whole darn database?Is there a way to prevent this writing to disk besides autocommit off, which only works to a limited degree? If not, my next post will probably be about how to do what I'm trying to do! ;-)ThanksSandy Sandra L. Pitner

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:

[OT] Form POSTing with LONG variable (2007) Summary search -- speed (1997) Two prices in shoppingcart? (1997) NT b19 sends extra MIME headers (1997) platform of the server? (2000) delete a file? (1998) auto-stripping of spaces (1997) Emailer port change (1997) Updating checkboxes made easy !!! (1998) [WebDNA] [OT] Multiple SSL certs on same server? (2014) Database Options (1997) converting tabs (1997) New syntax feedback for 4.0 (2000) WebCatalog2 Feature Feedback (1996) emailer (1997) More Applescript (1997) [WebDNA] OT: FCKeditor (2008) Navigator 4.01 (1997) Shipcost lookup? (1997) problem serving foreign languages text (1997)