1

Topic: Adding of statuses

We write system in which customer invented statuses. Let there will be an order status. They go from 0 to 10. At some instant the customer changes the process so that is interposed five new statuses between before the first status. The customer asks to observe sequence in digits for . It is necessary for them for different reports and . That is not pleasant, if it is stupid to make shift with 1 in old statuses on 6 in new that depart all  and broad gulls. That is  it is unambiguous, and broad gulls it is necessary , since they in basis. Well and a heap of places to look on system where there is a knot on statuses. While the unique thought in the table of statuses to column StatusId to add column UIStatusId and in server code to write converter StatusId <=> UIStatusId. There are still thoughts?

2

Re: Adding of statuses

Hello, Rikomer, you wrote: R> While unique thought in the table of statuses to column StatusId to add column UIStatusId and in server code to write converter StatusId <=> UIStatusId. Norms, and it was necessary to do initially. The substitute primary key + that there  wants.

3

Re: Adding of statuses

Hello, Rikomer, you wrote: R> While unique thought in the table of statuses to column StatusId to add column UIStatusId and in server code to write converter StatusId <=> UIStatusId. The column is not necessary. One more table which will compare StatusId <=> UIStatusId is necessary and on its basis to make the converter for display/input

4

Re: Adding of statuses

Hello, Rikomer, you wrote: R> There are still thoughts? It is possible to put down initially still statuses 0-10-20-... 100. Then in between it is possible to interpose about 10 intermediate. A crutch certainly, but quickly and an operation minimum.

5

Re: Adding of statuses

Hello, Rikomer, you wrote: R> They go from 0 to 10. R> At some instant the customer changes the process so that is interposed five new statuses between before the first status. R> the customer asks to observe sequence in digits for . It is necessary for them for different reports and . . There was such programming language the Fortran Earlier, and in it the main control flow statement was GOTO, and labels were , instead of as now. And, certainly, it was pleasant to all, that labels went on increase though language of it and did not demand. And as the people understood that in the course of program editing there can be new labels the people placed labels not 1-2-3, but 10-20-30. Accordingly, if between 10 and 20 it was necessary to interpose , interposed 15. , where it, old school...

6

Re: Adding of statuses

Hello, Rikomer, you wrote: R> we Write system in which customer invented statuses. R> let there will be an order status. R> they go from 0 to 10. R> At some instant the customer changes the process so that is interposed five new statuses between before the first status. R> the customer asks to observe sequence in digits for . It is necessary for them for different reports and . R> That is not pleasant, if it is stupid to make shift with 1 in old statuses on 6 in new that depart all  and broad gulls. R> that is  it is unambiguous, and broad gulls it is necessary , since they in basis. Well and a heap of places to look on system where there is a knot on statuses. R> while unique thought in the table of statuses to column StatusId to add column UIStatusId and in server code to write converter StatusId <=> UIStatusId. R> There are still thoughts? Perhaps something on subject High-Low algorithm? Probably, to provide some nesting levels hi-lo. https://vladmihalcea.com/the-hilo-algorithm/ https://stackoverflow.com/questions/282 … -algorithm

7

Re: Adding of statuses

Hello, Pzz, you wrote: Pzz> Eh, where it, old school... A post above

8

Re: Adding of statuses

Hello, itslave, you wrote: I> It is possible to put down initially still statuses 0-10-20-... 100. Then in between it is possible to interpose about 10 intermediate. A crutch certainly, but quickly and an operation minimum. A BASIC.