Re: FlushDatabase Suggestion
This WebDNA talk-list message is from 1998
It keeps the original formatting.
numero = 18043
interpreted = N
texte = I think you would need to have. new tag - [lock db=yourdb.db] locks a database keeping it from being read/written to/from disk until machine is restarted or until it recieves a [load db] command. Closedatabase nor flushdatase commands could not override this setting.[copyfile path=new/yourdb.db&to=yourdb.db]newtag [load db=yourdb.db]Barring this it would be very difficult for someone to beat your copyfile command, if you wanted to be sure your could do the following. With this scheme you backup your file before you remove and replace it. Then you close the database removing it from ram. After which you delete the file, preventing anyone from reloading it. It would be tough to beat the time between the closedatabase command and the deletefile command. This scenario would best meet the strictest available conditions, however if you crashed at the deletefile and before the copyfile you would not have access to the yourdb.db file and would have to retrieve it from the backup folder in order to get it going again. This is somewhat retentive but it does take into account all of your possible concerns.[copyfile path=yourdb.db&to=backup/archive.db](just for protection) [closedatabase path/to/some.db] [deletefile path=yourdb.db] [copyfile path=path/to/some.db&to=../somefolder/archive.db]Pat McCormick wrote:> Kenneth Grome wrote: > > > [closedatabase path/to/some.db] > > [copyfile path=path/to/some.db&to=../somefolder/archive.db] > > > > And yes, the [copyfile] tag *does* create the archive file if it didn't exist -- but the [closedatabase] tag does not, and that's why these two tags must be used together in order to achieve the results you asked for ... :) > > Ken, > > I have two folders: new & current, each containing a respective copy of a > catalog database. I want an URL which will dump the current, RAM database, > load the new one from the new directory, then save it to the current > directory, and make all subesequent accesses to the currect db. > > Will you solution achieve this - even if hits arrive during the close and copy process? > > -Pat
Associated Messages, from the most recent to the oldest:
I think you would need to have. new tag - [lock db=yourdb.db] locks a database keeping it from being read/written to/from disk until machine is restarted or until it recieves a [load db] command. Closedatabase nor flushdatase commands could not override this setting.[copyfile path=new/yourdb.db&to=yourdb.db]newtag [load db=yourdb.db]Barring this it would be very difficult for someone to beat your copyfile command, if you wanted to be sure your could do the following. With this scheme you backup your file before you remove and replace it. Then you close the database removing it from ram. After which you delete the file, preventing anyone from reloading it. It would be tough to beat the time between the closedatabase command and the deletefile command. This scenario would best meet the strictest available conditions, however if you crashed at the deletefile and before the copyfile you would not have access to the yourdb.db file and would have to retrieve it from the backup folder in order to get it going again. This is somewhat retentive but it does take into account all of your possible concerns.[copyfile path=yourdb.db&to=backup/archive.db](just for protection) [closedatabase path/to/some.db] [deletefile path=yourdb.db] [copyfile path=path/to/some.db&to=../somefolder/archive.db]Pat McCormick wrote:> Kenneth Grome wrote: > > > [closedatabase path/to/some.db] > > [copyfile path=path/to/some.db&to=../somefolder/archive.db] > > > > And yes, the
[copyfile] tag *does* create the archive file if it didn't exist -- but the
[closedatabase] tag does not, and that's why these two tags must be used together in order to achieve the results you asked for ... :) > > Ken, > > I have two folders: new & current, each containing a respective copy of a > catalog database. I want an URL which will dump the current, RAM database, > load the new one from the new directory, then save it to the current > directory, and make all subesequent accesses to the currect db. > > Will you solution achieve this - even if hits arrive during the close and copy process? > > -Pat
Bob Minor
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:
emailer (1997)
2.1 pricing? (1998)
More questions about serial number dishing (1997)
[shownext] support - MacOS (1997)
Exists? (1997)
Showif for mulitple variations (1997)
Enterprise Server (1998)
problems with WebCat-Plugin ()
Bulletin Board.... (2000)
I have observed and I am gone. (1998)
Smith Micro - no competition (2000)
Search in 2 or more catalogs (1997)
Stumpted Again (1997)
WCS Newbie question (1997)
sorting and summarizing (1998)
Why don't my carts expire (1998)
Searching multiple fields (1997)
customizing the color of user's pages (1997)
Server slowing down. (1997)
[WebDNA] Rewrite url (2013)