Re: Re: Re: Visited nodes

FYI: this is how the voting is done (I checked this long ago, and I might have missed something but this is what I remeber of it):

The db doesn't keep track of what you have voted, each "voteable" node has a field where user_id's who voted are stacked, comma-seperated or something like that. So when you try to vote, it checks against that field to see if you've voted, so there isn't a table for you holding what you've voted on, there's a field for the node holding who voted on it, it's simpler that way.

So, once again, you cannot "piggyback on the votes database table" cause there ain't any. I'm not assuming "it needs a radical change". I know it does, and you can ask other pmdevers.

He who asks will be a fool for five minutes, but he who doesn't ask will remain a fool for life.

Chady | http://chady.net/

Comment on Re: Re: Re: Visited nodes

Replies are listed 'Best First'.
(tye)Re: Visited nodes by tye (Sage) on Sep 02, 2002 at 19:37 UTC
Yes, there is too a 'vote' table. It also is currently the largest table in the database and backing that up is the only part of the database backup that really impacts the site (it is why the site locks up for a few minutes every night at around 23:30 PDT -- yes, we know how to fix that, it will get fixed eventually). And it currently only records votes. If you balloon it up to record "visits", then it would grow probably a couple of orders of magnitude. No, I certainly have no plans to make the largest table in the system a couple of orders of magnitude larger for the sake of tracking which nodes you've visited. Feel free to write a proxy module that does this for you client side. - tye (but my friends call me "Tye")	[reply]
Re: Re: Re: Re: Visited nodes by bart (Canon) on Aug 26, 2002 at 13:44 UTC
The db doesn't keep track of what you have voted, each "voteable" node has a field where user_id's who voted are stacked, comma-seperated or something like that. Ah, OK. Oh well.	[reply]