Re: Updating a database once per day - An example

This WebDNA talk-list message is from

1998


It keeps the original formatting.
numero = 17971
interpreted = N
texte = >>>>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 ... > >Okay, so if my template closes a database on a busy server, then >[movefile]s in a newly uploaded copy of the database, it's possible for >WebCatalog to reopen this database between the closing and the file >transfer if it receives another request for it?Good question, I will have to leave this one for the guys at PCS ... :)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)
>>>>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 ... > >Okay, so if my template closes a database on a busy server, then >[movefile]s in a newly uploaded copy of the database, it's possible for >WebCatalog to reopen this database between the closing and the file >transfer if it receives another request for it?Good question, I will have to leave this one for the guys at PCS ... :)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:

Mozilla/4. and Browser Info.txt (1997) [UPPERCASE] (1997) PIXO support (1997) Which WebCat is it? (2000) Date Calulation (1997) JavaScript: Select All Checkboxes (2001) Searching multiple Databases (1997) Updating a database once per day - An example (1998) Image maps/Webcat (1997) Multiple download orders of the same product? (1997) Forcing Paragraph Breaks on Results (1998) Re:listfiles-looking for slick solution (1997) Location of Browser Info.txt file (1997) Help with ShowNext (1998) WebCat Ad! (2000) 2.0.1 new commands and contexts (1997) Note added to [sendmail] in Docs (2004) why is this line in GeneralStore? (1998) Error Log.db --however (1997) WebCatalog2 Feature Feedback (1996)