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 Grome808-737-6499WebDNA Solutionsmailto:ken@webdna.nethttp://www.webdna.net
Associated Messages, from the most recent to the oldest:
>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 Grome808-737-6499WebDNA Solutionsmailto:ken@webdna.nethttp://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:
Converting spaces to + in results list (SOLVED) (2000)
Public beta 3 of WebCatalog 4.0 is now available (2000)
[LOOKUP] (1997)
WebCat2b12--[searchstring] bug (1997)
Document Contains No Data (1998)
Summing fields (1997)
Targeted Redirect (1999)
Large founditems loops (2000)
Help name our technology! (1997)
[WebDNA] PCI Vulnerability testing (2009)
when to use SQL over webcat? (2000)
Further tests with the infamous shipCost (1997)
Re:Problem (1997)
Explorer oddities (1997)
Limitations on fields? Server is crashing (1997)
WebCat2b13MacPlugIn - [include] (1997)
Mozilla/4. and Browser Info.txt (1997)
WebCat2b13MacPlugIn - [shownext method=post] ??? (1997)
WC Database Format (1997)
Sorting Results (1999)