|
|
Dear Partner,
We appreciate your contribution by reporting an Issue and also by giving the solution to it, and we will include it in our Product as soon as we can.
But we've changed the severity status of the Issue from critical to trivial and the priority from high to low, and this is the reason why.
Although what you report is an Issue, and we will fix it, it is a minor Issue. It is true that using the Id column to order the data is not the best option, since it is an auto generated value and it is random.
But, please realize that we first order the query by movement date. And that is the only important column to order the query by.
The reason we also order by another column is that, if two records have the same movement date, it is not important which one comes first, but is important that they always return in the same order, no matter how many time the query is executed, that is why we added an additional column to the order clause, to maintain consistency.
As you report, this is not the best option due to the random nature of the id, and we will fix it with the document number as you propose. But, also keep in mind that the id is generated once when the record is inserted, so in with the same set of data, you will get the same order of records for the query all the times.
Thanks you four your contribution.
Regards. |
|
MA_PRODUCTION_COST_GENERATE.diff (772) 2014-02-25 22:25