You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 6, 2020. It is now read-only.
In our database inventary numbers are, historically given, 1,2,3 etc. When sorting this field in table view it gets sorted as, e.g., 1,129,2,3,4,5,6,7,8 etc. Could the sort algorithm be improved so that leading zeros are not necessary to sort correctly?
The text was updated successfully, but these errors were encountered:
On Wed, Apr 8, 2020, 4:48 PM piratenpanda ***@***.***> wrote:
In our database inventary numbers are, historically given, 1,2,3 etc. When
sorting this field in table view it gets sorted as, e.g.,
1,129,2,3,4,5,6,7,8 etc. Could the sort algorithm be improved so that
leading zeros are not necessary to sort correctly?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#143>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AF6GJEFZUUHTDEX7742UQK3RLTPLRANCNFSM4MEHFJ6A>
.
Ok i should have mentioned that there are also entries with K1, or W1,W2 that's why the decision was made to use text instead of integer. So it's impossible?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In our database inventary numbers are, historically given, 1,2,3 etc. When sorting this field in table view it gets sorted as, e.g., 1,129,2,3,4,5,6,7,8 etc. Could the sort algorithm be improved so that leading zeros are not necessary to sort correctly?
The text was updated successfully, but these errors were encountered: