Timeline for Entity Framework - Is there a safety mechanism to prevent accidentally running Update-Database?
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 25 at 17:06 | vote | accept | EMN | ||
| Jul 23 at 7:13 | answer | added | jpmc26 | timeline score: 8 | |
| Jul 23 at 0:44 | answer | added | Flater | timeline score: 20 | |
| Jul 22 at 23:35 | answer | added | Nacht | timeline score: 3 | |
| Jul 22 at 23:25 | comment | added | Nacht | It's crazy to think that this is how our team used to do migrations. Use automated deployments! Never do this yourself! | |
| Jul 22 at 23:10 | history | became hot network question | |||
| Jul 22 at 17:26 | answer | added | Arseni Mourzenko | timeline score: 12 | |
| Jul 22 at 15:51 | review | Close votes | |||
| Jul 27 at 3:06 | |||||
| Jul 22 at 15:49 | comment | added | Greg Burghardt | "This could happen if you open the production solution in Visual Studio by mistake" --- a "production" solution? What do you mean by this? Typically DB connection strings are set at deploy time in a CI/CD pipeline. I cannot think of a good reason that opening your Visual Studio solution should ever connect to a production database for precisely the reason you are asking this question; what if you change something? DB changes should be applied at deploy time. | |
| Jul 22 at 15:10 | history | asked | EMN | CC BY-SA 4.0 |