enhancement
major
minor
major
minor
defect
Since #26377, migration scripts stored in the engine are no longer loaded when an application is started on a new software version, because the migration directories are no longer identified as such.
Data Migration
If an application’s data set has been set up anew with the code version TL_7.5.0-M1, this data set effectively contains no data version. Simply booting with a new code version now attempts to execute all migrations “from the very beginning.” This usually results in an error. In this case, the data version must be entered into the database before restarting the application:
INSERT INTO TL_PROPERTIES
("node", "propKey", "propValue")
VALUES('__global__', 'databaseVersion.tl-model-search', 'Ticket_25800_inconsistent_signature_create_handler');
INSERT INTO TL_PROPERTIES
("node", "propKey", "propValue")
VALUES('__global__', 'databaseVersion.tl', 'Ticket_26117_security_object');
INSERT INTO TL_PROPERTIES
("node", "propKey", "propValue")
VALUES('__global__', 'databaseVersion.tl-bpe', 'Ticket_25210_Model_references_in_form_definitions');
INSERT INTO TL_PROPERTIES
("node", "propKey", "propValue")
VALUES('__global__', 'databaseVersion.tl-element', 'Ticket_26460_remove_TLStructuredType_part');
INSERT INTO TL_PROPERTIES
("node", "propKey", "propValue")
VALUES('__global__', 'databaseVersion.tl-contact', 'Ticket_26398_remove_table_interfaces');
Test
- Create an application.
- Boot and shut down the application.
- Create a migration script in the application (Launch Config "Create migration template (...)").
- Start the application.
- The execution of the migration script must be logged.
See also #26798