Re: Updating a database once per day - An example

This WebDNA talk-list message is from

1998


It keeps the original formatting.
numero = 17969
interpreted = N
texte = On 5/30/1998 11:58 pm, 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 ...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?Rob Marquardt Designer/Resident Wirehead Toast Design300 First Avenue North, Suite 150 Minneapolis MN 55401 612.330.9863 v 612.321.9424 f www.toastdesign.com 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 11:58 pm, 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 ...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?Rob Marquardt Designer/Resident Wirehead Toast Design300 First Avenue North, Suite 150 Minneapolis MN 55401 612.330.9863 v 612.321.9424 f www.toastdesign.com Rob Marquardt

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:

taxRate is fine but taxTotal isn't (1997) Including a php script (2003) webcatalog [date] bug (1999) 2nd WebCatalog2 Feature Request (1996) WebCatalog can't find database (1997) required fields??? (2000) vars (2000) problems with WebCat-Plugin (1997) WebCat2final1 crashes (1997) Database (1999) 3.0 to 4.0 (2000) How to implement 'email to a friend' feature? (2002) WebCat2b12plugin - [search] is broken ... not! (1997) set header in DB (no cart) (2003) Date Formats (1997) Text data with spaces in them... (1997) upgrading (1997) What file? (1997) If Empty ? (1997) Date Search (2004)