Timeline for Recurring database migration
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 24, 2015 at 14:03 | vote | accept | trejder | ||
| Mar 24, 2015 at 14:03 | comment | added | trejder | Yes, you're right. And sorry. In Yii, the migration system works like this: each successfully applied migration is added to internal migration table in database, which assures, that each migration wil be applied only once. This, of course does not cover migrations, that fails at any point. Therefore, to implement, what I was suggested, such recurring migration would have to tamper with timestamp in that internal migration table, to make itself "always on top". Hope, that clears some doubts. | |
| Mar 24, 2015 at 9:49 | answer | added | Doc Brown | timeline score: 2 | |
| Mar 24, 2015 at 9:41 | comment | added | Doc Brown | You assume everyone knows how this kind of "database migration system" works. But in fact, what you are asking may depend on knowing the details of your framework (at least that's what I would expect). | |
| Mar 24, 2015 at 9:14 | comment | added | trejder | I'm using database migrations in Yii and Yii2 PHP frameworks. However, that shouldn't matter (?) as I'm asking for a general rule of a thumb here (that's why posting on Programmers, not on SO). | |
| Mar 24, 2015 at 8:53 | review | Close votes | |||
| Mar 28, 2015 at 21:16 | |||||
| Mar 24, 2015 at 7:16 | comment | added | Doc Brown | Are you using the term "database migrations" in a generic meaning, or are you having the term in mind like it is used in context of a specific technology like entity framework? | |
| Mar 24, 2015 at 6:30 | history | asked | trejder | CC BY-SA 3.0 |