The thing with SQL... is that you really don't need use external files -- just write directly to the database.
In links 2.0 you got a much greater performance boost by doing the updates once in a while, rather than every time.
With SQL, there is almost no reason to not do dynamic updates to the main database for hits, quantities, etc.
The Hits_Track table in LinkSQL tracks duplicate hits, not hits since last build.
I don't understand why there is a Build_Update, other than it was a logic-hold over from Links 2.0.
I've by passed it for everything I've done <G>
Since the Admin area no longer prints out all the "updated" stats, I wonder if that table will eventually be phassed out.
One thing I never did do is get the "ratings/votes" system integrated in the 1.11 release. I had it on a test copy of my 1.0 release. I was tracking all votes from 1-10, and recalculating the average vote and the hit distribution each update.
I put it on the back burner waiting for Jerry's mod, since it was much more complete than mine.
In links 2.0 you got a much greater performance boost by doing the updates once in a while, rather than every time.
With SQL, there is almost no reason to not do dynamic updates to the main database for hits, quantities, etc.
The Hits_Track table in LinkSQL tracks duplicate hits, not hits since last build.
I don't understand why there is a Build_Update, other than it was a logic-hold over from Links 2.0.
I've by passed it for everything I've done <G>
Since the Admin area no longer prints out all the "updated" stats, I wonder if that table will eventually be phassed out.
One thing I never did do is get the "ratings/votes" system integrated in the 1.11 release. I had it on a test copy of my 1.0 release. I was tracking all votes from 1-10, and recalculating the average vote and the hit distribution each update.
I put it on the back burner waiting for Jerry's mod, since it was much more complete than mine.
