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 - Welcome New SI Members!

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: SI Bob who wrote (18656)6/10/2003 5:05:46 PM
From: Jon Tara  Read Replies (1) of 32918
 
You gotta admit, I was darn close, Bob.

I don't think you have to look any further for the cause of the delays - you've found it.

BTW, when I said GUI, your "text-based URL stuff" would qualify for what I was thinking off. But it doesn't seem to be the problem, given your explanation of what happens with the message-renumbering.

What I had in mind was this: you do a "delete a post". The database gets locked. You get an "are you sure" button. The database is still locked until you select "yes" or "cancel".

Probably an improbable situation given that it's a web-based interface. It'd be REALLY dumb to do this, HTTP being a sessionless protocol, and you'd NEVER select "yes" or "cancel".

Of course, it's equally dumb in an executable. But people do it all the time. :( The lock would generally be released when the program is closed. But not when Bob goes for coffee.

So, I thought the stop-gap solution might have been "don't go for coffee while you are doing this".

I agree, renumbering keys in a large database is a particularly eggregarious design flaw. Somebody didn't understand the relational model.

In the mean time, maybe you could do your deleting at night. :)
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext