Feature is implemented. No need to argue.
It will be included in the next release.

or code will server-side depended in this case anywhere. bad way. IMHO.

1) why reason for paging mode then?
2) it simplle select from-to recorrds in DB oreder. fast result. - IT reason page mode!
3) if make sort or another (want more& - write SQL manualy) no page-mode-perfomance.

USER-FAKE.

"1. User NOT always can fetch all records" and? Anyway your have subset of select.

1) in simple way it "first N", but usually it "select N to M".
2) GUI improve your access to DB ordered data in paged mode
3) for sort "page" it MUST select ALL data first, sort it and show result after.
4) it it base-structure depended.
5) it not GUI task
6) since engine.

Implementation reasons:
1. User NOT always can fetch all records from table because of table size
2. In paginal mode you get wrong results when using local filtering/sorting

Feature is automatically turned off when user fetches all records from server.

hmm... why started?

it can be implemented with FROM s,e ORDER BY o...

BUT
- paginal mode 4: server side load reduce & client-side speed increace
- what if i want sort by not indexed long string field or BLOB?
- user always can use fetch all records from table with same time result or use SELECT statement itself.

don't see implementation reason.