Re: Updating a database once per day - An example

This WebDNA talk-list message is from

1998


It keeps the original formatting.
numero = 17968
interpreted = N
texte = On 5/30/1998 7:42 am, Kenneth Grome so noted...>In that case, the best method is to perform these tasks -- all in one >template: > >1- Put the new db in a different folder. >2- Close the current db. >3- Trash the current db you just closed. >4- Move the new db to the folder the old one was in before you trashed it. > > >>Now, what I am trying to accomplish, mydatabase.db (which happens to be >>copied from the MainFrame to the Web Server at 3:03AM each night with the >>name mydatabase.db) will be closed at 3:10am, and then re-openned with >>fresh contents the next time it is needed. > >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?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 7:42 am, Kenneth Grome so noted...>In that case, the best method is to perform these tasks -- all in one >template: > >1- Put the new db in a different folder. >2- Close the current db. >3- Trash the current db you just closed. >4- Move the new db to the folder the old one was in before you trashed it. > > >>Now, what I am trying to accomplish, mydatabase.db (which happens to be >>copied from the MainFrame to the Web Server at 3:03AM each night with the >>name mydatabase.db) will be closed at 3:10am, and then re-openned with >>fresh contents the next time it is needed. > >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?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:

Recalculating Shipping Costs (1997) Altivec (Velocity engine) (2000) [WebDNA] An actual attempt to get WebDNA and MAMP Pro to work - (2018) User/pass with tcpconnect (2000) Weird bug, or is there something amiss? (1997) RE: [WebDNA] [test] (2009) RE: Formulas.db + Users.db (1997) [WebDNA] XSS and getting rid of HTML codes (2018) [no_cache]?! (2000) Navigator Parsing (1997) Slightly OT: [sendmail] help (2003) Odd [math] behaviour (2003) # fields limited? (1997) Searching for a Blank Field (2000) Include a big block of text (1997) Summary layout (1997) [WebDNA] decrypt appears to be hosed (2008) [WebDNA] OT: FCKeditor (2008) Help (1999) Re:Copyright ? (1997)