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: Jon Tara who wrote (18646)6/10/2003 4:49:01 PM
From: SI Bob  Read Replies (3) of 32918
 
It's a problem that existed when I was here before and I see it's still a problem. There are no GUI's for the site. All text-based URL stuff.

The technical and accurate explanation is that, for reasons that completely escape me and always have, the message table contains a separate field that is a long integer (besides the obvious one we use to identify messages by number) and is apparently a key field. Some parts of the system use this field to identify messages.

The deletion process physically removes the record from the table and puts it into another table. More than is needed (iHub simply toggles a flag that prevents the message from displaying) but not particularly expensive as infrequently as it's used.

What's expensive is that when a message is deleted, every message after it gets that "extra" field renumbered.

I complained about this a lot while I was working here before. The solution they came up with was to insist that I not delete messages during the day.

To me, this is a very major flaw in database structure. It happened when it was initially moved to Oracle. We'll have to duplicate this flaw when we migrate it back to MS-SQL because we have no idea what routines will get "broken" with removal of this field yet.

It goes without saying that this isn't a flaw that will be allowed to survive any longer than necessary, though.
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext