[IMP] stock_available_to_promise_release: Improve migration/init script to initialize 'release_policy' field with default values

[rousseldenis]

The upgrade script should initialize the value with the sql default instead updating every existing record (maybe billions).

[rousseldenis]

@jbaudoux @mt-software-de

[rousseldenis]

This is the magic:

[mt-software-de]

Many thanks yes this was missing.
Why did not set the release_policy as it is done here?

wms/stock_available_to_promise_release/migrations/16.0.3.1.0/post-migrate.py

Line 5 in 111d877

def migrate(cr, version):

[rousseldenis]

Many thanks yes this was missing. Why did not set the release_policy as it is done here?

wms/stock_available_to_promise_release/migrations/16.0.3.1.0/post-migrate.py

Line 5 in 111d877

def migrate(cr, version):

Here, I initialize the field with the default value, so, it should be done in pre script.

I've put it also in pre-init as the module can be installed on huge database too

[mt-software-de]

Many thanks yes this was missing. Why did not set the release_policy as it is done here?

wms/stock_available_to_promise_release/migrations/16.0.3.1.0/post-migrate.py

Line 5 in 111d877

def migrate(cr, version):

Here, I initialize the field with the default value, so, it should be done in pre script.

I've put it also in pre-init as the module can be installed on huge database too

Many thanks yes this was missing. Why did not set the release_policy as it is done here?

wms/stock_available_to_promise_release/migrations/16.0.3.1.0/post-migrate.py

Line 5 in 111d877

def migrate(cr, version):

Here, I initialize the field with the default value, so, it should be done in pre script.

I've put it also in pre-init as the module can be installed on huge database too

Yes i have seen this, but why we don't remove the post_migration
and moving the post_migration part into the new init method?