Enhancement
Major
Detail
Major
Detail
Bugfix
Migration scripts stored in the engine are no longer imported when starting an application on a new software version since #26377, because the migration directories are no longer identified as such.
Data migration
If a data state of an application has been rebuilt with the code state of TL_7.5.0-M1, this data state de-facto does not contain a data version. A simple boot with a new code state now tries to execute all migrations "from the beginning of time". This usually leads to 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 application.
- Boot and shutdown application.
- Create migration script in application (Launch-Config "Create migration template (...)").
- Start application.
- The execution of the migration script must be announced in the log.
See also #26798