Re: Updating a database once per day - An example

This WebDNA talk-list message is from

1998


It keeps the original formatting.
numero = 17970
interpreted = N
texte = >On 5/30/1998 7:42 am, Kenneth Grome so noted... >>Okay, so what you must do is put that newly-created db into a *different* >>folder than the file it's replacing. Then when you write your WebDNA code, >>you can do all the tasks above, all in a single template. This is very >>important, because you must make sure that after WebCatalog closes the >>current db, another request does NOT open it again before WebCat has >>replaced it. > >Just to make sure I have this correct before implementing site-wide (I've >been pondering this same problem for the past week as well)... > >As long as all these operations happen in a single template, there's no >chance of another page trying to get at the database while it's in >limbo? No matter how many threads the webserver's running or how many >hits per second, when you get right down to the nitty gritty it's only >possible for WebCatalog to be handling a single task at once?No, it performs multi-threading tasks very easily most of the time, because anything that's not purging the data from RAM can always be performed simultaneously. But when you're closing a database, it has to wait for the *other* threads to finish what they've started with that db, then it closes the db ...Sincerely, Ken Grome 808-737-6499 WebDNA Solutions mailto:ken@webdna.net http://www.webdna.net Associated Messages, from the most recent to the oldest:

    
  1. Re: Updating a database once per day - An example ( 1998)
  2. Re: Updating a database once per day - An example (bob 1998)
  3. Re: Updating a database once per day - An example (Kenneth Grome 1998)
  4. Re: Updating a database once per day - An example (Steve Rosenbaum 1998)
  5. Re: Updating a database once per day - An example (Kenneth Grome 1998)
  6. Re: Updating a database once per day - An example (Marty Schmid 1998)
  7. Re: Updating a database once per day - An example (Kenneth Grome 1998)
  8. Re: Updating a database once per day - An example (Kenneth Grome 1998)
  9. Re: Updating a database once per day - An example (Gary Richter 1998)
  10. Re: Updating a database once per day - An example (Peter Ostry 1998)
  11. Re: Updating a database once per day - An example (Kenneth Grome 1998)
  12. Re: Updating a database once per day - An example (Kenneth Grome 1998)
  13. Re: Updating a database once per day - An example (Rob Marquardt 1998)
  14. Re: Updating a database once per day - An example (Peter Ostry 1998)
  15. Re: Updating a database once per day - An example (Kenneth Grome 1998)
  16. Re: Updating a database once per day - An example (Kenneth Grome 1998)
  17. Re: Updating a database once per day - An example (Rob Marquardt 1998)
  18. Re: Updating a database once per day - An example (Rob Marquardt 1998)
  19. Re: Updating a database once per day - An example (Kenneth Grome 1998)
  20. Re: Updating a database once per day - An example (Steve Rosenbaum 1998)
  21. Re: Updating a database once per day - An example (Kenneth Grome 1998)
  22. Updating a database once per day - An example (Steve Rosenbaum 1998)
>On 5/30/1998 7:42 am, Kenneth Grome so noted... >>Okay, so what you must do is put that newly-created db into a *different* >>folder than the file it's replacing. Then when you write your WebDNA code, >>you can do all the tasks above, all in a single template. This is very >>important, because you must make sure that after WebCatalog closes the >>current db, another request does NOT open it again before WebCat has >>replaced it. > >Just to make sure I have this correct before implementing site-wide (I've >been pondering this same problem for the past week as well)... > >As long as all these operations happen in a single template, there's no >chance of another page trying to get at the database while it's in >limbo? No matter how many threads the webserver's running or how many >hits per second, when you get right down to the nitty gritty it's only >possible for WebCatalog to be handling a single task at once?No, it performs multi-threading tasks very easily most of the time, because anything that's not purging the data from RAM can always be performed simultaneously. But when you're closing a database, it has to wait for the *other* threads to finish what they've started with that db, then it closes the db ...Sincerely, Ken Grome 808-737-6499 WebDNA Solutions mailto:ken@webdna.net http://www.webdna.net Kenneth Grome

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:

(1997) Merging databases (1997) RE: [WebDNA] Anyone using version 6.2.1 in production on Linux (2013) WebCat2 - [format thousands] (1997) Setting up WebCatalog with Retail Pro data (1996) [ShowIf] and empty fields (1997) Date stamp and purging (1998) Running 2 two WebCatalog.acgi's (1996) Generating Options for a Form. (1997) Newbie HW/SW Setup Question (2000) Limit to Field Length in DB (1998) Problems reading files created by WC (1997) What am I missing (1997) Online reference (1997) Which Version? 5.1 or 6.0? (2004) Possible Bug in 2.0b15.acgi (1997) Encrypt broken on Mac 3.05b13?? (2000) why is this line in GeneralStore? (1998) Pass Thru Page? (1998) New Command prefs ... (1997)