Hi Guys,
When devices are organised by IP it doesnt seem to work. It gets the ordering all messed up.
https://1drv.ms/i/s!AgwFONjNYqXLjblO_c0vpIjw7lFvHQ
Devices organised by IP
- ukzerosniper
- Posts: 28
- Joined: Sat Jul 30, 2016 6:46 pm
- Location: England
- Contact:
If this post helped. Consider donating to my bit coin fund
1DrTMxNmBuZwgEcJs2LTh3hnB6VFEC1Uqf
1DrTMxNmBuZwgEcJs2LTh3hnB6VFEC1Uqf
This is currently a known issue:
https://tracker.unimus.net/browse/UN-105
The problem basically is that we allow both IPs and hostnames for device addresses.
Sorting is done on the database layer, since we off-load all sorting and paging operations to the database itself.
(since every database does this best natively, and we support multiple)
We are working on fixing it, however it's proving to be difficult.
We wanted to write proper queries for each database, that will sort numbers naturally and hostnames as well, while at the same time not breaking paging.
Since we support multiple databases, this proved impossible, due to inherrent differences between database engines.
We will go with stored procedures to fix this, however it is being more difficult to properly implement than we originally anticipated.
(since this includes updating all database schemas, adding stored procedures as part of DB upgrade, testing on all DBs in all cases, etc.)
Long story short:
It will be fixed in one of upcoming releases
https://tracker.unimus.net/browse/UN-105
The problem basically is that we allow both IPs and hostnames for device addresses.
Sorting is done on the database layer, since we off-load all sorting and paging operations to the database itself.
(since every database does this best natively, and we support multiple)
We are working on fixing it, however it's proving to be difficult.
We wanted to write proper queries for each database, that will sort numbers naturally and hostnames as well, while at the same time not breaking paging.
Since we support multiple databases, this proved impossible, due to inherrent differences between database engines.
We will go with stored procedures to fix this, however it is being more difficult to properly implement than we originally anticipated.
(since this includes updating all database schemas, adding stored procedures as part of DB upgrade, testing on all DBs in all cases, etc.)
Long story short:
It will be fixed in one of upcoming releases
- ukzerosniper
- Posts: 28
- Joined: Sat Jul 30, 2016 6:46 pm
- Location: England
- Contact:
lol, nice one. As long as your on it.
If this post helped. Consider donating to my bit coin fund
1DrTMxNmBuZwgEcJs2LTh3hnB6VFEC1Uqf
1DrTMxNmBuZwgEcJs2LTh3hnB6VFEC1Uqf