Silicon Investor (SI) -- The First Internet Community

STOCKTALK

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) -- Ignore unavailable to you. Want to Upgrade?

To: John Biddle who wrote (315)	4/29/2004 11:56:15 AM
From: SI Bob	Read Replies (1) \| Respond to of 6035

Since tracking the last-read message number is an "update" function, it's one of several routines I'm saving for the 11th hour. The only similar functions I've currently implemented are the ones to reset new message counts to zero and to remove bookmarks. But those actions get overwritten hourly with each new import of the bookmarks table. Anything that involves updating a table that could "collide" with activity from the production site is being held off to the last minute since I'm going to have to jump through extra hoops for those. A good example is message-posting. I could start writing the message-posting routines right now and have them working in less than a day, but the routine that imports from the production site (roughly every 5-10 minutes) looks at the last message number on Dev, and imports all messages past that number. The workaround I'll have to do is to have a separate table keeping track of messages that were written on the Dev site and, at the beginning of every import, remove those messages.