in reply to Implementation of a Ladder System
I think I would handle it with a couple of tables. One for the users information and another table with a column for a Storable serialized object. I would create a datastructure with the rankings of the users and then store it to the database. The next time through I would retrieve that data structure, reorder however necessary and then store it back. You can use that datastructure to order (rank) your users and it only requires one update and one select for the ordering. I'm not sure how many user id's you could store in a single field, it would depend I guess on what you stored in your data structure. This would remove the flat file and would probably increase your performance. I haven't used this for anything myself as of yet, but it seems like it might be a good way to do what your looking for.
HTH,
Steve
|