Re: ExclusiveLock
This WebDNA talk-list message is from 2003
It keeps the original formatting.
numero = 52928
interpreted = N
texte = My understanding is that WebDNA does an implied exclusive lock around each append, replace or delete. The only times I generally use [exclusivelock] are when I'm doing some more complex operation, usually involving multiple databases, and I want to ensure that all necessary databases are available and nobody messes with them while I'm updating. For example: [exclusivelock order.db,oitems.db,member.db] .... code that updates the order, the items and the member, as when they submit an order ... [/exclusivelock] SMSI: Care to comment? - brian On Tuesday, September 16, 2003, at 12:11 PM, Donovan wrote: > WebDna @ wrote: >> Yes well, the fact that you used it lead to the question. :) >> I wanted to know if it is needed. I am one of those who like to have >> as >> little code as possible. > > Ah, :-) I would be interested also. I started using it after seeing > in > Johns DBEdit code (after some commit issues). > > There is probably a greater sience of knowing when to use the different > flush commit close databases and knowing when to use Exclusivelock. > > This also is impacted by your preference settings. If you choose > "Automatically commit databases to disk after modification", you > probably can take out the commitdatabase after your [append] etc. > I have this pref turned on AND I use the manual [commit]. I suppose > that I would consider taking the contexts out if the pages were slow. > > One good thing about using them though is that the code is more > portable... (the next server the code lies on might not have this > pref enabled). > > I would assume Exclusivelock is more for databases that get edited > from multiple locations at near the same time. > > Donovan > -- Brian Fries, BrainScan Software -- http://www.brainscansoftware.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://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
My understanding is that WebDNA does an implied exclusive lock around each append, replace or delete. The only times I generally use [exclusivelock] are when I'm doing some more complex operation, usually involving multiple databases, and I want to ensure that all necessary databases are available and nobody messes with them while I'm updating. For example: [exclusivelock order.db,oitems.db,member.db] .... code that updates the order, the items and the member, as when they submit an order ... [/exclusivelock] SMSI: Care to comment? - brian On Tuesday, September 16, 2003, at 12:11 PM, Donovan wrote: > WebDna @ wrote: >> Yes well, the fact that you used it lead to the question. :) >> I wanted to know if it is needed. I am one of those who like to have >> as >> little code as possible. > > Ah, :-) I would be interested also. I started using it after seeing > in > Johns DBEdit code (after some commit issues). > > There is probably a greater sience of knowing when to use the different > flush commit close databases and knowing when to use Exclusivelock. > > This also is impacted by your preference settings. If you choose > "Automatically commit databases to disk after modification", you > probably can take out the commitdatabase after your [append] etc. > I have this pref turned on AND I use the manual [commit]. I suppose > that I would consider taking the contexts out if the pages were slow. > > One good thing about using them though is that the code is more > portable... (the next server the code lies on might not have this > pref enabled). > > I would assume Exclusivelock is more for databases that get edited > from multiple locations at near the same time. > > Donovan > -- Brian Fries, BrainScan Software -- http://www.brainscansoftware.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://webdna.smithmicro.com/
Brian Fries
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:
[WebDNA] TCPConnect w/ user:pass (2009)
OT: Heads-up to Smith Micro staff (2002)
random sorting broken (was Re[2]: php vs WebCatalog) (2000)
WebCat2 several catalogs? (1997)
Searching Multiple DBs (1997)
RE: [WebDNA] [ReturnRaw] problem (2010)
can WC render sites out? (1997)
# fields limited? (1997)
Fwd: more ! testing (1997)
Shownext - am i missing something? (1998)
hideif glitch (2003)
Copyright that puppy (1998)
Loss in form (1998)
Nested tags count question (1997)
japanese characters (1997)
Server crash (1997)
Text data with spaces in them... (1997)
Conversion Database Blues (2001)
Problem with encrypted cookies (2000)
Sorting a Search... (1998)