Re: 'page impression' techniques for banner ads

This WebDNA talk-list message is from

1999


It keeps the original formatting.
numero = 22202
interpreted = N
texte = >Re: >>How does closedatabase and commit database affect speed? If a server crashes >>and use the #1 technique then I'll lose a lot of the data. So if I add a >>commitdatabase call would that be the same as going to the disk like option >>2? > >OK.... (or as Support 2 used to say, Ah ha.. gotcha) > >WHY can't the databases be automatically saved to disk and the ram freed >when a replace, append, write etc... contexts is (are) sent?In a sense, they can. In the WebCatalog admin area, turn on autocommit databases. This will save any modification to any database to disk immediately. Please note, you will pay a HEAVY speed penalty if you are doing operations like comparing one database to another and integrating record changes to synchronize the two. Perhaps a future version of webcatalog will allow you (in the admin area) to turn on autocommit for each database, or give us a command to temporarily turn off autocommit databases while an operation is taking place. [commitoff db=somedata.db]blah blah blah[commiton db=somedata.db]BTW, closedatabase will not lose any data, as it commits the ram to disk, then flushes the ram of the database. Commitdatabase only saves from ram to disk, but it leaves the database in ram afterward.Why close the whole database because you did a replace? All you need to do it write the database to disk (for safety) which commitdatabase will do. Brian B. Burton BOFH - Department of Redundancy Department --------------------------------------------------------------- MMT Solutions - Specializing in Online Shopping Solutions 973-808-8644 http://www.safecommerce.comAre you a Web Programmer? I am today. Associated Messages, from the most recent to the oldest:

    
  1. Re: 'page impression' techniques for banner ads (PCS Technical Support 1999)
  2. Re: 'page impression' techniques for banner ads (Sandra L. Pitner 1999)
  3. Re: 'page impression' techniques for banner ads (PCS Technical Support 1999)
  4. Re: 'page impression' techniques for banner ads (PCS Technical Support 1999)
  5. Re: 'page impression' techniques for banner ads (Kenneth Grome 1999)
  6. Re: 'page impression' techniques for banner ads (Brian B. Burton 1999)
  7. Re: 'page impression' techniques for banner ads (Brian B. Burton 1999)
  8. Re: 'page impression' techniques for banner ads (Kenneth Grome 1999)
  9. Re: 'page impression' techniques for banner ads (Kenneth Grome 1999)
  10. Re: 'page impression' techniques for banner ads (Kenneth Grome 1999)
  11. Re: 'page impression' techniques for banner ads (Brian B. Burton 1999)
  12. Re: 'page impression' techniques for banner ads (The Mooseman 1999)
  13. Re: 'page impression' techniques for banner ads (olin 1999)
  14. Re: 'page impression' techniques for banner ads (PCS Technical Support 1999)
  15. 'page impression' techniques for banner ads (Kenneth Grome 1999)
>Re: >>How does closedatabase and commit database affect speed? If a server crashes >>and use the #1 technique then I'll lose a lot of the data. So if I add a >>commitdatabase call would that be the same as going to the disk like option >>2? > >OK.... (or as Support 2 used to say, Ah ha.. gotcha) > >WHY can't the databases be automatically saved to disk and the ram freed >when a replace, append, write etc... contexts is (are) sent?In a sense, they can. In the WebCatalog admin area, turn on autocommit databases. This will save any modification to any database to disk immediately. Please note, you will pay a HEAVY speed penalty if you are doing operations like comparing one database to another and integrating record changes to synchronize the two. Perhaps a future version of webcatalog will allow you (in the admin area) to turn on autocommit for each database, or give us a command to temporarily turn off autocommit databases while an operation is taking place. [commitoff db=somedata.db]blah blah blah[commiton db=somedata.db]BTW, closedatabase will not lose any data, as it commits the ram to disk, then flushes the ram of the database. Commitdatabase only saves from ram to disk, but it leaves the database in ram afterward.Why close the whole database because you did a replace? All you need to do it write the database to disk (for safety) which commitdatabase will do. Brian B. Burton BOFH - Department of Redundancy Department --------------------------------------------------------------- MMT Solutions - Specializing in Online Shopping Solutions 973-808-8644 http://www.safecommerce.comAre you a Web Programmer? I am today. Brian B. Burton

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:

Smart caching problems with 2.1b3? (1997) CommitDatabase vs. CloseDatabase (2001) Using Applescript to process WebCatalog functions (1998) javascript problem copying values (2000) WebCat editing, SiteGuard WAS:SiteAssociative lookup style? (1997) emailer setup (1997) no global [username] or [password] displayed ... (1997) [REPLACE] inside [FOUNDITEMS] (1998) PCS Frames-Default page is solution! (1997) WebCatalog stalls (1998) How do I specify a & character in Grep? (2000) WebCat2 beta 11 - new prefs ... (1997) Associative lookup style? (1997) Subtotal Not Calculated on Invoice.html (1998) Wanted: More Math Functions (or, Can You Solve This?) (1997) Find all in search. (2002) SetLineItem (1997) carriage returns in data (1997) Cross-platform file names? (2000) Limit in size of a database (1999)