Some ideas to improve the migration script generator:
The scripts can be generated directly into the folder where we expect to be committed when running in eclipse -> migration/iD10/oracle and migration/iD10/postgresql
When running on a server - they can still be written in /tmp - but better in the proper structure and naming expected to commit -> /tmp/migration/iD10/oracle and /tmp/migration/iD10/postgresql
The script can be generated directly with the name convention, like 202202121125_IDEMPIERE-1111.sql - here we can take the ticket number from the first part of the migration script comment
The script can generate the register_migration_script line at the beginning of the script, instead of letting the developer to add it at the end - the effect is the same because we run the scripts completely even if they fail in the middle
Environment
None
Activity
Show:
Heng Sin Low February 13, 2022 at 10:14 PM
Hi , no, I don’t have anything to add at the moment.
Carlos Ruiz February 13, 2022 at 3:29 PM
Hi - I did the changes described above - anything additional you want to suggest about migration scripts?
Some ideas to improve the migration script generator:
The scripts can be generated directly into the folder where we expect to be committed when running in eclipse -> migration/iD10/oracle and migration/iD10/postgresql
When running on a server - they can still be written in /tmp - but better in the proper structure and naming expected to commit -> /tmp/migration/iD10/oracle and /tmp/migration/iD10/postgresql
The script can be generated directly with the name convention, like 202202121125_IDEMPIERE-1111.sql - here we can take the ticket number from the first part of the migration script comment
The script can generate the register_migration_script line at the beginning of the script, instead of letting the developer to add it at the end - the effect is the same because we run the scripts completely even if they fail in the middle