Tango.info table sort
Server side vs jquery
user feedback:
I think your objective should be to give satisfactory performance to all, not better performance to some. Serverside SQL is good because the time for a sort is never more than the time for the first page, hence you can be sure that anyone who was satified by the time of the first page will be satisfied by the time of the sorted page.
Another advantage of server side is that in the worst cases - where the page is long as in the Canaro example - the part of the page the user is seeing when he clicks for a sort refreshes much sooner than JS, because JS refresh takes place only when the operation has completed.
also
pro server
- jquery sort on some table columns is buggy
pro js
- in chrome js much faster
- saves server cpu
- search results have several tables all with their own sorting, js only sorts on part of the page. what would server side do?
- only call results for the table in question?
- Chrisjjj It already sorts each table idependently and so would resort each table independently, e.g. GET or POST variables would carry sort parameters for each table.
Accents
https://tango.info/performances/FrancLomut/voc.FernaDiaza
user via form: "wenn man per javascript alphabetisch sortiert, wird Intimas wegen des Akzentes am Ende einsortiert."
Test sort with Wiki-ja
| Num | Test char |
|---|---|
| 1 | A |
| 2 | Íntimas |
| 3 | Z |
As of 2014-06-20: same problem.