Re: [WebDNA] Re: exclusivelock
This WebDNA talk-list message is from 2011
It keeps the original formatting.
numero = 107016
interpreted = N
texte = You got me on the hook! On 7/21/11 10:16 AM, Govinda wrote: > Great questions Ken! > I would also really like to read a definitive (more comprehensive) article on that context. > > -Govinda > > > On 2011-07-21, at 7:24 AM, Kenneth Grome wrote: > >>> Should I use exclusivelock on a db I want to replace? >> Are there other reasons why I should not use exclusivelock >> as shown in the example below? >> >> Are there better ways to insure that this.db gets replaced >> completely in RAM and on disk before the next visitor >> requests a page that opens this.db again? >> >> Does anyone have a clue about how exclusivelock actually >> works? For example, can WebDNA acquire an exclusivelock on >> a database that is closed? Or does it have to open the db >> in order to acquire the lock? >> >> What happens when a db is open when the exclusivelock is >> acquired? Can the db be closed and the file deleted inside >> the exclusivelock context? >> >> Sorry if these questions seem anal, but using exclusivelock >> at all suggests that we need to do something critically >> important to the db, and if it doesn't work the way we think >> it does, we could be making really bad assumptions and >> possibly putting our data at risk. >> >> I never used exclusivelock before, and it seems that not >> many other people have either. But after Grant's post last >> week I get the feeling that we should be using it in a lot >> of situations where we are not. So I'm just trying to get a >> clearl understanding of its limitations, and how it actually >> works. >> >> Sincerely, >> Kenneth Grome >> >> >> >>> Should I use exclusivelock on a db I want to replace? Is >>> this the proper way to use exclusivelock? >>> >>> [exclusivelock db=this.db] >>> [closedatabase this.db] >>> [deletefile this.db] >>> [copyfile from=new.db&to=this.db] >>> [/exclusivelock] >>> >>> ... or does exclusivelock hold this.db OPEN thus >>> preventing it from closing and therefore preventing it >>> from being replaced by the new.db? >>> >>> Sincerely, >>> Kenneth Grome > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list
. > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us
Associated Messages, from the most recent to the oldest:
You got me on the hook! On 7/21/11 10:16 AM, Govinda wrote: > Great questions Ken! > I would also really like to read a definitive (more comprehensive) article on that context. > > -Govinda > > > On 2011-07-21, at 7:24 AM, Kenneth Grome wrote: > >>> Should I use exclusivelock on a db I want to replace? >> Are there other reasons why I should not use exclusivelock >> as shown in the example below? >> >> Are there better ways to insure that this.db gets replaced >> completely in RAM and on disk before the next visitor >> requests a page that opens this.db again? >> >> Does anyone have a clue about how exclusivelock actually >> works? For example, can WebDNA acquire an exclusivelock on >> a database that is closed? Or does it have to open the db >> in order to acquire the lock? >> >> What happens when a db is open when the exclusivelock is >> acquired? Can the db be closed and the file deleted inside >> the exclusivelock context? >> >> Sorry if these questions seem anal, but using exclusivelock >> at all suggests that we need to do something critically >> important to the db, and if it doesn't work the way we think >> it does, we could be making really bad assumptions and >> possibly putting our data at risk. >> >> I never used exclusivelock before, and it seems that not >> many other people have either. But after Grant's post last >> week I get the feeling that we should be using it in a lot >> of situations where we are not. So I'm just trying to get a >> clearl understanding of its limitations, and how it actually >> works. >> >> Sincerely, >> Kenneth Grome >> >> >> >>> Should I use exclusivelock on a db I want to replace? Is >>> this the proper way to use exclusivelock? >>> >>> [exclusivelock db=this.db] >>> [closedatabase this.db] >>> [deletefile this.db] >>> [copyfile from=new.db&to=this.db] >>> [/exclusivelock] >>> >>> ... or does exclusivelock hold this.db OPEN thus >>> preventing it from closing and therefore preventing it >>> from being replaced by the new.db? >>> >>> Sincerely, >>> Kenneth Grome > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list. > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us
Aaron Michael Kaczmarek
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:
Migrating to NT (1997)
.. more on sliding discounts... (1997)
Payflow Pro on OSX (2003)
[WebDNA] Need some PHP help (2009)
(2000)
Uniqueness of Cart number (2000)
Introduction/Tutorial/QuickStart (1997)
An Isnumeric function of some kind (2001)
Combining search criteria in a context? (1998)
Bug Report, maybe (1997)
Dark Horse Comics success story (1997)
AUTHENTICATE TAG Problem (2000)
Multiple prices (1997)
[Webcat 2]Next (1997)
Webcat deletes last line from Excel-saved text db (2004)
[WebDNA] Processor Maxing out (2010)
Calculating Shipping (1997)
RE: [countChars] from