SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
SI - Site Forums : Silicon Investor - Legacy Interface Discussion (2004-2011)
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: SI Dave who wrote (2241)10/13/2004 12:32:37 PM
From: SI Bob   of 6035
 
That's going to really, really suck if it's a timing issue. Message insertion is such a rare event in the big picture of the kind of work the db box does and can do that it *should* be safe to work from an understanding that the db box will never be asked to do more than one at a time. Even an 18ms gap should be enormous.

But it's also possible that even an ISP outage lasting a relatively short amount of time can result in a collision-causing mini-flood whenever the lights turn back on.

I'd better do a little reading and see if I need to wrap the message insertion routines in transactions and use explicit locks. If this is the solution for this problem, it'll also be the solution to the problem of the occasional intra-thread message number duplication.
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  

HomeMailHotSubjectMarksPeopleMarksKeepersSettings
Terms Of UseContact UsCopyright/IP PolicyPrivacy PolicyAbout UsFAQAdvertise on SI
© 2026 Knight Sac Media.  Data provided by Twelve Data, Alpha Vantage, and CityFALCON News