Re: Closing Databases

This WebDNA talk-list message is from

1998


It keeps the original formatting.
numero = 16597
interpreted = N
texte = >>You only need to worry if the database in WebCatalog has been modified -- >>using something like [Append] [Replace] [Delete], etc. If the database is>>'read-only', then simply uploading a new file and then doing a >>[CloseDatabase] or [FlushDatabases] will re-read the new file. > >Sorry, I still do not understand why I would have to close of flush the >database afterwards. Closing/Flusing a database writes what's in memory >back to disk. If I first upload a new file and then close or flash the >database, to my understanding the file in memory is overwriting the new >file with old data?! What's wrong with my way of thinking. > >JohnThis is a problem that has been plagueing PCS since I first joined this list, and could be fixed in one easy step, that for some reason, PCS doesn't see or won't implement. The problem is based on the confusion of the term closedatabase. The way PCS has the closedatabase tag define, it is dual purpose (which is a good thing from a minimalist point of view), to both write changed databases and to flush unchanged databases (no need to write to disk.) But the users don't get it! (and most users don't want it this way!) Why not have two tags, [closedatabase] which saves any database to disk again, and [reloaddatabase] which throws away the ram copy (changes or not) and reloads the database of the same name. Or perhaps [closedatabase commit=T] or [closedatabase commit=F]. Personally, I'd like a reload tag so I could upload a new database, issue the command, and know that the ram file is flused, and the new database is opened, with practically no downtime. I'll now await PCS's reply about why they don't want to do this. (it will have nothing to do with it not being possible...) Brian B. Burton BOFH --------------------------------------------------------------- MMT Solutions - Specializing in Online Shopping Solutions 973-808-8644 http://www.safecommerce.com Associated Messages, from the most recent to the oldest:

    
  1. Re: Closing databases (Glenn Busbin 2003)
  2. Re: Closing databases (Frank Nordberg 2003)
  3. Re: Closing databases (Glenn Busbin 2003)
  4. Re: Closing databases (Frank Nordberg 2003)
  5. Re: Closing databases (Glenn Busbin 2003)
  6. Closing databases (Frank Nordberg 2003)
  7. Re: Closing Databases (Jay Van Vark 1998)
  8. Re: Closing Databases (Brian B. Burton 1998)
  9. Re: Closing Databases (Bob Minor 1998)
  10. Re: Closing Databases (Sjoerd Jan ter Welle 1998)
  11. Re: Closing Databases (PCS Technical Support 1998)
  12. Re: Closing Databases (Sjoerd Jan ter Welle 1998)
  13. Re: Closing Databases (Grant Hulbert 1998)
  14. Re: Closing Databases (Olin Lagon 1998)
  15. Re: Closing Databases (Kenneth Grome 1998)
  16. Re: Closing Databases (Sjoerd Jan ter Welle 1998)
  17. Re: Closing Databases (Kenneth Grome 1998)
  18. Closing Databases (take 2) (Brian B. Burton 1998)
>>You only need to worry if the database in WebCatalog has been modified -- >>using something like [append] [replace] [delete], etc. If the database is>>'read-only', then simply uploading a new file and then doing a >>[closedatabase] or [flushdatabases] will re-read the new file. > >Sorry, I still do not understand why I would have to close of flush the >database afterwards. Closing/Flusing a database writes what's in memory >back to disk. If I first upload a new file and then close or flash the >database, to my understanding the file in memory is overwriting the new >file with old data?! What's wrong with my way of thinking. > >JohnThis is a problem that has been plagueing PCS since I first joined this list, and could be fixed in one easy step, that for some reason, PCS doesn't see or won't implement. The problem is based on the confusion of the term closedatabase. The way PCS has the closedatabase tag define, it is dual purpose (which is a good thing from a minimalist point of view), to both write changed databases and to flush unchanged databases (no need to write to disk.) But the users don't get it! (and most users don't want it this way!) Why not have two tags, [closedatabase] which saves any database to disk again, and [reloaddatabase] which throws away the ram copy (changes or not) and reloads the database of the same name. Or perhaps [closedatabase commit=T] or [closedatabase commit=F]. Personally, I'd like a reload tag so I could upload a new database, issue the command, and know that the ram file is flused, and the new database is opened, with practically no downtime. I'll now await PCS's reply about why they don't want to do this. (it will have nothing to do with it not being possible...) Brian B. Burton BOFH --------------------------------------------------------------- MMT Solutions - Specializing in Online Shopping Solutions 973-808-8644 http://www.safecommerce.com 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:

Bug in the docs ... (2002) problem: search crashes webstar (1997) Multiple Merchant Accounts? (1997) searching within same page (2000) Safari browser and WebDNA set-cookies (2003) [WebDNA] Apple nixes Mac OS Server ("websites") and other (2018) Beta Documentation (1997) [WebDNA] PayPal IPN (was: paypal FINALLY!!!!) (2009) followup to ws3 vs ws2.1 speed (1998) Weird Math and SV (1997) ODBC and WebCatalog on Solaris and talking to a Sybase database (2001) lookup command (1997) Interfacing WebMerchant to www.fedex.com (1997) WebStar Secure on other machine (1997) select multiple 2 more cents (1997) Getting Emailer to send mail (1997) Wanted: More Math Functions (or, Can You Solve This?) (1997) two unique banners on one page (1997) encrypt (2000) Giving out error pages (1997)