Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Revisions: Issue #41103 [ All Revisions ] [ Back to Issue ]
Summary 0041103: QtyDelivered has changed its representation on DB
Revision 2019-06-17 16:03 by guillermogil
Description QtyDelivered has changed its representation on DB and now is saved with decimal values and before 19Q1 it did not have decimal values at database level.
As an example:
On 18Q4 qtyDelivered at DB level was 1
On 19Q1 qtyDelivered at DB level is 1.0

As the representation of the value have changed some third party integration could be broken.

It will happen with every column saved with a "BigDecimal.valueof"
Previously it was a "new BigDecimal"

It will be needed to check OrderLoader to review all the properties that have changed.
We've identified QtyDelivered column but it is needed to check for more.
Revision 2019-06-17 14:52 by guillermogil
Description QtyDelivered has changed its representation on DB and now is saved with decimal values and before 19Q1 it did not have decimal values at database level.
As an example:
On 18Q4 qtyDelivered at DB level was 1
On 19Q1 qtyDelivered at DB level is 1.0

As the representation of the value have changed every third party integration it can be broken.

It will happen with every column saved with a "BigDecimal.valueof"
Previously it was a "new BigDecimal"

It will be needed to check OrderLoader to review all the properties that have changed.
We've identified QtyDelivered column but it is needed to check for more.
Revision 2019-06-17 14:39 by guillermogil
Description QtyDelivered has changed its representation on DB and now is saved with decimal values and before 19Q1 it did not have decimal values at database level.
As an example:
On 18Q4 qtyDelivered at DB level was 1
On 19Q1 qtyDelivered at DB level is 1.0

As the representation of the value have changed every third party integration it can be broken.

It will happen with every column saved with a "BigDecimal.valueof"
Previously it was a "new BigDecimal"

It will be needed to check OrderLoader to review all the properties that have changed.
We've identified QtyDelivered and QtyInvoiced but it is needed to check all.
Revision 2019-06-17 14:37 by guillermogil
Description QtyDelivered has changed its representation on DB and now is saved with decimal values and before 19Q1 it did not have decimal values at database level.
As an example:
On 17Q2 qtyDelivered at DB level was 1
On 19Q1 qtyDelivered at DB level is 1.0

As the representation of the value have changed every third party integration it can be broken.

It will happen with every column saved with a "BigDecimal.valueof"
Previously it was a "new BigDecimal"

It will be needed to check OrderLoader to review all the properties that have changed.
We've identified QtyDelivered and QtyInvoiced but it is needed to check all.
Revision 2019-06-17 13:51 by guillermogil
Description QtyDelivered is saved with decimal and before 19Q1 it did not have decimal values.
As an example:
On 17Q2 qtyDelivered at DB level was 1
On 19Q1 qtyDelivered at DB level is 1.0

As the representation of the value have changed every third party integration it can be broken.

It will happen with every column saved with a "BigDecimal.valueof"
Previously it was a "new BigDecimal"

It will be needed to check OrderLoader to review all the properties that have changed.
We've identified QtyDelivered and QtyInvoiced but it is needed to check all.
Revision 2019-06-17 13:39 by guillermogil
Description QtyDelivered is saved with decimal and before 19Q1 it did not have decimal values.
As an example:
On 17Q2 qtyDelivered at DB level was 1
On 19Q1 qtyDelivered at DB level is 1.0

It will happen with every column saved with a "BigDecimal.valueof"
Previously it was a "new BigDecimal"

It will be needed to check OrderLoader to review all the properties that have changed.
We've identified QtyDelivered and QtyInvoiced but it is needed to check all.
Revision 2019-06-17 13:37 by guillermogil
Description QtyDelivered is saved with decimal and before 19Q1 it did not have decimal values.
As an example:
On 17Q2 qtyDelivered at DB level was 1
On 19Q1 qtyDelivered at DB level is 1.0

It will happen with every column saved with a "BigDecimal.valueof"
Previously it was a "new BigDecimal"

It will be needed to check OrderLoader to review all the properties that have changed.
Revision 2019-06-17 13:37 by guillermogil
Description QtyDelivered is saved with decimal and before 19Q1 it did not have decimal values.
As an example:
On 17Q2 qtyDelivered at DB level was 1
On 19Q1 qtyDelivered at DB level is 1.0

It will happen with every column saved with a "BigDecimal.valueof"
Previously it was a "new BigDecimal"

It will be needed to check OrderLoader to review all that have changed.
Revision 2019-06-17 13:33 by guillermogil
Description QtyDelivered is saved with decimal and before 19Q1 it did not have decimal values.
As an example:
On 17Q2 qtyDelivered at DB level was 1
On 19Q1 qtyDelivered at DB level es 1.0

It will happen with every column saved with a "BigDecimal.valueof"
Previously it was a "new BigDecimal"

It will be needed to check OrderLoader to review all that have changed.
Revision 2019-06-17 13:29 by guillermogil
Description QtyDelivered is saved with decimal and before 19Q1 it did not have decimal.
On 17Q2 qtyDelivered at DB level was 1
On 19Q1 qtyDelivered at DB level es 1.0

It will happen with every column save with a BigDecimal.valueof
Previously it was a new BigDecimal

It will be needed to check OrderLoader to review all that have changed.
Revision 2019-06-17 13:29 by guillermogil
Description QtyDelivered is saved with decimal and before 19Q1 it did not have decimal.
On 17Q2 qtyDelivered at DB level was 1
On 19Q1 qtyDelivered at DB level es 1.0

It will happen with every column save with a BigDecimal.valueof
Previously it was a new BigDecimal

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker