Database Locking?!?
This WebDNA talk-list message is from 2000
It keeps the original formatting.
numero = 26112
interpreted = N
texte = This has been discussed before and I'm bringing it up again...Database locking.Let me make a few quick assumptions for my problem to prevent solutionsthat I can't use:1. I MUST use my sequential number solution as the record ID.2. Refer to #13. I can't really reduce the size of the database for other reasons.Based on the above assumptions, I do a search on a database in order todetermine the next sequential number, and then I append the record withthat new ID number, and all it's information (a lot of information).Unfortunately, it seems that this append takes so long (much less than asecond, but long enough to cause this problem), if another person hits thepage, they TOO will get that same ID since the new one wasn't appended tothe database before they hit that page. It's gotten to a point where Iactually can get 6 duplicate IDs, and that's just plain bad.My question is, I need to do database locking somehow. If I do mysearch INSIDE of the append, will that lock access to the database untilthe append completes, and therefore solve my duplicate ID problem?If not, any other ideas on this (but sticking to the top 3 assumptions)?Thanks. Appreciate any help on this one that I can get.-Howard-------------------------------------------------------------Brought to you by CommuniGate Pro - The Buzz Word Compliant Messaging Server.To end your Mail problems go to
.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
Associated Messages, from the most recent to the oldest:
This has been discussed before and I'm bringing it up again...Database locking.Let me make a few quick assumptions for my problem to prevent solutionsthat I can't use:1. I MUST use my sequential number solution as the record ID.2. Refer to #13. I can't really reduce the size of the database for other reasons.Based on the above assumptions, I do a search on a database in order todetermine the next sequential number, and then I append the record withthat new ID number, and all it's information (a lot of information).Unfortunately, it seems that this append takes so long (much less than asecond, but long enough to cause this problem), if another person hits thepage, they TOO will get that same ID since the new one wasn't appended tothe database before they hit that page. It's gotten to a point where Iactually can get 6 duplicate IDs, and that's just plain bad.My question is, I need to do database locking somehow. If I do mysearch INSIDE of the append, will that lock access to the database untilthe append completes, and therefore solve my duplicate ID problem?If not, any other ideas on this (but sticking to the top 3 assumptions)?Thanks. Appreciate any help on this one that I can get.-Howard-------------------------------------------------------------Brought to you by CommuniGate Pro - The Buzz Word Compliant Messaging Server.To end your Mail problems go to .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
Howard Wolosky
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] Listfields does not work with tables (2011)
New public beta available (1997)
Problem (1997)
A question for the experts (2000)
WebCat b15 Mac plug-in (1997)
# of real domains on 1 web server (1997)
Up and running ... at last !! (1997)
SearchTitle Question (1998)
Error Messages Returned to User (1997)
possible, WebCat2.0 and checkboxes-restated (1997)
still facing truncated [texta] problem (2000)
Two submit buttons ? (1997)
Emailer again (1997)
[date] formatting bug inside [orderfile]? (1998)
Strange behavior (2000)
Problem with HTML email (2003)
PIXO support (1997)
WebMerchant MacAuthorize Hub (1999)
4.0 upgrade pricing (2000)
empty shopping cart message (1997)