On 2014/09/25 15:43, James K. Lowden wrote:
On Thu, 25 Sep 2014 10:36:31 +0200
Clemens Ladisch <clem...@ladisch.de> wrote:
Yes, and yes, absolutely. In that case the order is established by the
user, and can be captured by the application as integers, and stored in
the database. The problem is trivial because the number is limited
to what a human being is willing to sort "by hand". And the SQL is
straightforward.
--jkl
I think his example was meant to show the validity of the notion, not be a
stringent use-case.
To this end, I will explain what I'm trying to do, and I have been thinking of making the system determine ordering up front as to
avoid the whole issue. Basically we need to record live race results - but not a normal race, imagine a like a bingo game, every now
and then someone finishes but the time of finishing does not determine position alone, there are bonuses and penalties which doesn't
stack up to integer values, but is measurable.. so there is an action of finding a best-fit position in the list for the newest
finisher and "insert" him/her there. The next finisher may well be below or above. Without going into too much detail about how
bonuses and penalties are calculated or rather, affected, think of a turn-based strategy card game as is common these days (Pokemon,
Magic, etc.) with possible penalties such as "skip a turn", how do you put that into number values? It's much harder to make a
mathematical positioning result than simply working out if the current is better or worse than any existing position.
Harder, but not impossible, and if this ordering conundrum turns out to have too high an effort/pleasure ratio, then finding a
mathematical positioning algorithm is next.
Thanks for all the input!
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
