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:

Cart # Starting at 1000 (2000) eCommerce Solution (2000) Thanks for tips, more quest (1997) WebCat2b12--[searchstring] bug (1997) Separate server for jpg/gif files (1998) MySQL question (2005) Add a field to the error log? (1997) PIXO support (1997) Hotmail and HTML emails (2003) Subtotals (1999) Assigning new CART number (1997) [OT] SQL and Crackers (2000) Re:Searchable Archives (1998) Max Record length restated as maybe bug (1997) webCatalog and Stocks (1998) method of payment (1997) Document Contains No Data! (1997) Replace with Producteditor.tpl (2000) imagemagick / iis / plesk - - - path solved (2006) Associative lookup style? + bit more (1997)