Feature #39609
Migration Version
| Status: | Accepted | Start date: | 2012-08-08 | ||
|---|---|---|---|---|---|
| Priority: | Should have | Due date: | |||
| Assigned To: | Karsten Dambekalns | % Done: | 50% |
||
| Category: | - Migrations - | ||||
| Target version: | - | Estimated time: | 1.00 hour | ||
| PHP Version: | Complexity: | ||||
| Has patch: | No |
Description
For CD/CI it would be helpful if doctrine cli controller would report the current version of migration.
We've changed doctrine:migrationversion that way that if no version is provided the action will report current migration version.
By this it is possible to decide on script level if migration is required or not.
Find patch attached.
doctrine.migration.patch
(35.7 kB)
History
#1 Updated by Karsten Dambekalns almost 3 years ago
- Project changed from TYPO3 Flow Base Distribution to TYPO3.Flow
- Assigned To set to Karsten Dambekalns
#2 Updated by Karsten Dambekalns almost 3 years ago
- Category set to - Migrations -
- Status changed from New to Needs Feedback
- Target version deleted (
1.1) - Has patch set to No
If you only know the latest version applied, you do not yet know if a migration might be needed. There could be migrations "in between" that have been added by installed packages and have a lower identifier than the latest applied one.
What could work is a quiet flag to migrationstatus (similar to the quiet flag for migrate) that outputs the needed migrations, one per line.
#3 Updated by Karsten Dambekalns over 2 years ago
- Status changed from Needs Feedback to Accepted
- Target version set to 2.1
#4 Updated by Robert Lemke about 2 years ago
- Target version deleted (
2.1)