Datenbank #862
Datenbank #740: Question for Udo
Database Version Number
| Status: | Zurückgestellt | Start date: | ||
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | Alexander Blum | % Done: | 0% | |
| Category: | - | |||
| Target version: | Repertoire 2) Testing phase II |
Description
for programmatic db updates
History
#1 Updated by Alexander Blum over 4 years ago
- Target version changed from 2) Testing phase II to Repertoire 2) Testing phase II
#2 Updated by Alexander Blum over 4 years ago
- Project changed from repertoire to collecting_society
#3 Updated by Alexander Blum about 3 years ago
- Status changed from Neu to Feedback
- Assignee changed from Werkeverwaltung to Thomas Mielke
I showed you how migration is done in tryton. What's the task here?
#4 Updated by Thomas Mielke about 3 years ago
- Subject changed from Datenbank Version Number to Database Version Number
- Assignee changed from Thomas Mielke to Alexander Blum
You showed me the rather hacky approach with probing, yes. I'd still prefer a db that has a conciousness about its own version, allowing the application of db changes in an orderly fashion. But if you insist that we don't need it, just close this one.
#5 Updated by Alexander Blum about 3 years ago
- Status changed from Feedback to Zurückgestellt
- Parent task set to #740
we can talk with udo about this (added this task to the udo question ticket), but afaik it's not the way this is handled in tryton