Timeline for Entity Framework Code First Centralized database deployment
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 25, 2015 at 0:22 | vote | accept | Phoenix | ||
| Mar 25, 2015 at 0:22 | answer | added | Phoenix | timeline score: 1 | |
| Nov 4, 2014 at 12:42 | comment | added | Phoenix | By "other clients which haven't been updated yet", I mean older versions of my software(aka not latest version), which may still be connecting to the database. There is no old software or database. The update process for a network (multiple clients+single server), according to the solution I am thinking about is supposed to be something like this: 1. Update database. 2. Update every client to latest version of the software while displaying errors to clients trying to connect with old versions. I hope this clears it up a bit. | |
| Nov 4, 2014 at 12:38 | history | edited | Phoenix | CC BY-SA 3.0 |
added 2 characters in body
|
| Nov 4, 2014 at 11:28 | history | tweeted | twitter.com/#!/StackProgrammer/status/529596105122529280 | ||
| Nov 4, 2014 at 10:33 | comment | added | Patrick | You are assuming that the new software S2 can work with the old database D1 and that the old software S1 is incompatible with the new database D2. Both are assumptions might not be true. | |
| Nov 4, 2014 at 7:12 | review | First posts | |||
| Nov 4, 2014 at 10:09 | |||||
| Nov 4, 2014 at 7:12 | history | asked | Phoenix | CC BY-SA 3.0 |