Re: Simple Database close connection
This WebDNA talk-list message is from 2001
It keeps the original formatting.
numero = 39176
interpreted = N
texte = I think that a new tag, or optional parameter, to flush a database from memory without committing changes to disk is not an unreasonable request. Maybe [closedatabase db=....&commit=false]?Have you tried changing file permissions so that WebCatalog cannot commit changes, even if it tried?> -----Original Message----- > From: WebCatalog Talk [mailto:WebDNA-Talk@talk.smithmicro.com]On > Behalf Of John Peacock > Sent: Tuesday, October 09, 2001 7:35 AM > To: WebCatalog Talk > Subject: Re: Simple Database close connection > > > 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/------------------------------------------------------------- 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:
I think that a new tag, or optional parameter, to flush a database from memory without committing changes to disk is not an unreasonable request. Maybe [closedatabase db=....&commit=false]?Have you tried changing file permissions so that WebCatalog cannot commit changes, even if it tried?> -----Original Message----- > From: WebCatalog Talk [mailto:WebDNA-Talk@talk.smithmicro.com]On > Behalf Of John Peacock > Sent: Tuesday, October 09, 2001 7:35 AM > To: WebCatalog Talk > Subject: Re: Simple Database close connection > > > 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/------------------------------------------------------------- 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/
Scott Anderson
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:
Problems appending to database (1997)
my price won't move (1997)
Text data with spaces in them... (1997)
Multiple fields on 1 input (1997)
Add sizes from check boxes (2002)
Limiting user access to .tmpl files (1997)
hidden databases (2000)
Removing [showif] makes a big difference in speed (1997)
[append] (1997)
random random links (1999)
POST (1997)
Include remote? (1998)
Question about replacing words (1998)
Locking up with WebCatalog... (1997)
Re1000001: Setting up shop (1997)
Virtual hosting and webcatNT (1997)
Security Issues and WebCommerce Solution (1997)
BugNote#1 - listdatabases fails on MacOS ... (2000)
Changing user submitted data (2000)
[include ...] behavior (1997)