Created on 2020-09-15.12:33:49 by pokoli, last changed 1 month ago by pokoli.
On 2020-09-15 14:12, Sergi Almacellas Abellana wrote: > Then why we have the contraint on the transaction tables? Because it is data entry for the user so we must enforce the constraints.
Then why we have the contraint on the transaction tables? For example the stock move have the digits contraint so reducing the digits will also break all the existing records on the transaction tables.
This is not a safe design. An history value should never have constraint.
El 15/9/20 a les 13:15, Cédric Krier ha escrit: > It must not have digits as precision can change over time. IIUC precision can only increase over time. So there should not be any issue.
It must not have digits as precision can change over time. clients must be fixed if they do not display the correct number.
The Cost Price field of the Product Cost History model does not have any digits attribute set. This makes the clients display a diferent number (5 digits on tryton and 3 digits on tryton). This may cause to confusion to the user as a digit is missing on sao.
|2020-09-24 23:17:05||pokoli||set||status: testing -> closed|
|2020-09-15 15:21:02||ced||set||messages: + msg60134|
|2020-09-15 14:12:45||pokoli||set||messages: + msg60131|
|2020-09-15 14:10:14||ced||set||messages: + msg60130|
|2020-09-15 13:19:30||pokoli||set||messages: + msg60128|
messages: + msg60127
messages: + msg60126
|2020-09-15 12:35:17||pokoli||set||status: in-progress -> testing|
keyword: + review
Showing 10 items. Show all history (warning: this could be VERY long)