Re: Simple Database close connection
This WebDNA talk-list message is from 2001
It keeps the original formatting.
numero = 39156
interpreted = N
texte = Scott Anderson wrote: > > WebCatalog does not track changes made to the database file by users, other > programs, or even certain WebDNA tags (WriteFile, AppendFile, etc...). This > is why you should take care to make sure the database is flushed from memory > before modifying the physical database file by any means other than the > built in database commands.This is, of course, the cause of the problems that I have. If WebCatalog does not track changes made outside of its control (say by looking at the last modified timestamp), I have no good way to get WebCatalog to notice my changes other than [flushdatabase], which risks stomping on my changes should WebCatalog decide that the file in RAM was, at some point in the past modified for whatever reason.I need r/o databases. WebCatalog needs to keeps its claws off of them and NEVER write to a r/o database. I also need a tag to force the RAM resident version to be replaced with the disk resident copy. I cannot be expected to [flushdatabase] and THEN replace a 16MB database, all the while hoping that no one does a query that will reload a now partial file. This is a classic race condition and is not good design. Even a simple [reloaddatabase db=...] which would drop the RAM version and load the disk version would be better than the current state of affairs.This is not the first time I have asked for this (as Grant will probably be able to document) since ALL of our primary database are extracts from our backend systems and are NEVER modified within WebCatalog. I can, of course, shut off WebCatalog while I am in the process of replacing my files, but I am running many sites which pass all of their pages through WebCatalog, so that would leave me completely dead in the water during updates.John-- John Peacock Director of Information Research and Technology Rowman & Littlefield Publishing Group 4720 Boston Way Lanham, MD 20706 301-459-3366 x.5010 fax 301-429-5747------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list
. To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/
Associated Messages, from the most recent to the oldest:
Scott Anderson wrote: > > WebCatalog does not track changes made to the database file by users, other > programs, or even certain WebDNA tags (WriteFile, AppendFile, etc...). This > is why you should take care to make sure the database is flushed from memory > before modifying the physical database file by any means other than the > built in database commands.This is, of course, the cause of the problems that I have. If WebCatalog does not track changes made outside of its control (say by looking at the last modified timestamp), I have no good way to get WebCatalog to notice my changes other than [flushdatabase], which risks stomping on my changes should WebCatalog decide that the file in RAM was, at some point in the past modified for whatever reason.I need r/o databases. WebCatalog needs to keeps its claws off of them and NEVER write to a r/o database. I also need a tag to force the RAM resident version to be replaced with the disk resident copy. I cannot be expected to [flushdatabase] and THEN replace a 16MB database, all the while hoping that no one does a query that will reload a now partial file. This is a classic race condition and is not good design. Even a simple [reloaddatabase db=...] which would drop the RAM version and load the disk version would be better than the current state of affairs.This is not the first time I have asked for this (as Grant will probably be able to document) since ALL of our primary database are extracts from our backend systems and are NEVER modified within WebCatalog. I can, of course, shut off WebCatalog while I am in the process of replacing my files, but I am running many sites which pass all of their pages through WebCatalog, so that would leave me completely dead in the water during updates.John-- John Peacock Director of Information Research and Technology Rowman & Littlefield Publishing Group 4720 Boston Way Lanham, MD 20706 301-459-3366 x.5010 fax 301-429-5747------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/
John Peacock
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:
WebCat2b12 - nesting [tags] (1997)
won't serve .tpl -index.tpl gone, made test.tpl (2000)
[WebDNA] v.7 and eCommerce (2012)
Problems getting parameters passed into email. (1997)
WebCatalog/Mac 2.1b2 - PIXO (1997)
Bad Cookie / Internet Option / Internet Explorer (2004)
Location of Browser Info.txt file (1997)
Help! WebCat2 bug (1997)
Scrape Interest Rates (2005)
Multiple Newcarts (1996)
[BULK] [WebDNA] [BULK] WebDNA 7 Won't Install/Work [internal server error] (2010)
Search results templates (1996)
ASCII Code 127 (2004)
Public beta 2 for WebCatalog 4.0 is now available. (2000)
Search bug. Help (2002)
Sending emails (went[ot] ) (2002)
Is there a way to just get to the last record in the database? (1997)
[WebDNA] A 'globals' folder on the FastCGI version? (2015)
[searchString] (1997)
security (https) w webcat (1999)