Re: CommitDatabase vs. CloseDatabase

This WebDNA talk-list message is from

2001


It keeps the original formatting.
numero = 39553
interpreted = N
texte = >> >> >Also, it is not necessary to commit a database after EVERY >>>>>modification, unless you have some non-webcat program using the db >>>>>at random and arbitrary times. >>>> >>>>...and if you don't mind losing data in a crash - which was the >>>>starting point for this thread. >>> >>>so turn on autocommit and save yourself some typing. >> >>Yes. If you want to commit every database after every modification. >>Otherwise use commit or close as best suited to your needs - which >>is the bottom line of this thread. If you don't want to learn >>something and understand how to fine tune WebCat, please continue to >>jump to conclusions and drop smart comments. > >Settle down. No offense meant. > >How does turning off autocommit help prevent loosing data in any way?Turning autocommit off does of course not prevent losing data. But that's not the point.Autocommit commits every database after every modification. If you're running a low traffic server with small databases you won't probably notice this very much, but it can slow down a busy server with large databases a *lot*.Also, not every database is probably mission critical, so you can gain some speed by not commit these database as often as you commit your important ones.-- ************************************************************* Christer Olsson Stora Nygatan 21 Phone +46 40 791 50 Ljusa Idéer AB S-211 37 Malmoe Fax +46 40 97 99 77 Sweden http://www.ljusaideer.se------------------------------------------------------------- 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://search.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Re: CommitDatabase vs. CloseDatabase (Christer Olsson 2001)
  2. Re: CommitDatabase vs. CloseDatabase (Samuel Renkert 2001)
  3. Re: CommitDatabase vs. CloseDatabase (Christer Olsson 2001)
  4. Re: CommitDatabase vs. CloseDatabase (Samuel Renkert 2001)
  5. Re: CommitDatabase vs. CloseDatabase (Christer Olsson 2001)
  6. Re: CommitDatabase vs. CloseDatabase (Glenn Busbin 2001)
  7. Re: CommitDatabase vs. CloseDatabase (Samuel Renkert 2001)
  8. Re: CommitDatabase vs. CloseDatabase (Grant Hulbert 2001)
  9. Re: CommitDatabase vs. CloseDatabase (Alex McCombie 2001)
  10. Re: CommitDatabase vs. CloseDatabase (Glenn Busbin 2001)
  11. Re: CommitDatabase vs. CloseDatabase (Glenn Busbin 2001)
  12. Re: CommitDatabase vs. CloseDatabase (Samuel Renkert 2001)
  13. Re: CommitDatabase vs. CloseDatabase (Nitai @ ComputerOil 2001)
  14. Re: CommitDatabase vs. CloseDatabase (Nitai @ ComputerOil 2001)
  15. Re: CommitDatabase vs. CloseDatabase (Christer Olsson 2001)
  16. CommitDatabase vs. CloseDatabase (Glenn Busbin 2001)
>> >> >Also, it is not necessary to commit a database after EVERY >>>>>modification, unless you have some non-webcat program using the db >>>>>at random and arbitrary times. >>>> >>>>...and if you don't mind losing data in a crash - which was the >>>>starting point for this thread. >>> >>>so turn on autocommit and save yourself some typing. >> >>Yes. If you want to commit every database after every modification. >>Otherwise use commit or close as best suited to your needs - which >>is the bottom line of this thread. If you don't want to learn >>something and understand how to fine tune WebCat, please continue to >>jump to conclusions and drop smart comments. > >Settle down. No offense meant. > >How does turning off autocommit help prevent loosing data in any way?Turning autocommit off does of course not prevent losing data. But that's not the point.Autocommit commits every database after every modification. If you're running a low traffic server with small databases you won't probably notice this very much, but it can slow down a busy server with large databases a *lot*.Also, not every database is probably mission critical, so you can gain some speed by not commit these database as often as you commit your important ones.-- ************************************************************* Christer Olsson Stora Nygatan 21 Phone +46 40 791 50 Ljusa Idéer AB S-211 37 Malmoe Fax +46 40 97 99 77 Sweden http://www.ljusaideer.se------------------------------------------------------------- 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://search.smithmicro.com/ Christer Olsson

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:

Help name our technology! I found it (1997) Modulo function? (2000) WebCat b13 CGI -shownext- (1997) ODBC and WebCatalog on Solaris and talking to a Sybase database (2001) Any Unix/Linux version to come? (1999) Webstar 1.3.1 PPC (1997) Is this possible, WebCat2.0 and checkboxes (1997) Add htmlarea 3 to SiteBuilder (2004) writefile - continued (1997) Searching multiple fields from one form field (1997) CERT Advisory on malicious scripts (2000) Locking up with WebCatalog... (1997) [Announce]: Web server security and password protection (1997) emailer setup (1997) Suffix Mapping (1997) b12 cannot limit records returned and more. (1997) WebCat2b15MacPlugin - [protect] (1997) Calendar sample (1998) [WebDNA] feature requests (2008) Weighting of grouped results possible? (was: grouping fieldsquestion) (1998)