Exactly, which is why I can't think it through as to what's best, and perhaps it's better to ignore preferences and just go by oldest first.
Re: Likes
« Reply #15, on January 20th, 2012, 08:13 PM »
1. | Though because I'm doing it through the action=like handler rather than anything else, it got... upset... I had to expressly detect for and start the gzhandler buffer otherwise the browsers all cacked themselves at the content being incorrect. |
2. | The table structure is four columns: id-content, content-type, id-member, like-time. This way, likes can be extended to media or whatever else with little real effort in the DB. The trick here is that content-type is a fixed width field, currently 6 characters, which should be enough to be at least representative of content, currently only 'post' is supported but there's the foundation for hooks to be able to extend it arbitrarily. But because it's fixed width rows, with a primary key of id-content/content-type/id-member, and queried that way, it should be pretty lean. |