I am utilizing a customized decimal area in a customized product sort in Drupal commerce. It has a precision of 10 and a scale of two (2 digits to Drupal Developer proper of Drupal Developer decimal place).
I’ve a shopper with a lot of merchandise that use this area, however their specification has now modified to require a decimal to 3dp.
By default Drupal “locks” Drupal Developer area to keep away from knowledge loss:
As a result of Drupal Developer area already has knowledge, some settings can now not be modified.
I took to modifying Drupal Developer database, and it appears to have labored effective. I did three issues:
-
Modified Drupal Developer construction sort of
field_THIS_FIELD_value
area in Drupal Developerdrupal_field_data_THIS_FIELD
desk fromdecimal(10,2)
todecimal(11,3)
-
Repeated Drupal Developer similar for Drupal Developer area revision desk
-
I downloaded Drupal Developer BLOB from desk ‘drupal_field_config’ for
field_THIS_FIELD
and altered{s:9:"precision";s:2:"10";s:5:"scale";s:1:"2"
to{s:9:"precision";s:2:"11";s:5:"scale";s:1:"3"
I cleared cache and present knowledge now has an additional 0 after Drupal Developer decimal place, and after I alter Drupal Developer knowledge it shops it to three decimal locations.
So it appears to work effective. However am I lacking something? Is there wherever else the place area knowledge is modified that I would want to vary?
Does Drupal Developer system integrity stay intact? I believe I’ve completed what’s essential however do not wish to inadvertently break one thing else or trigger any weak point in Drupal Developer system.