Timeline for How do you approach one database per developer when working with a very large databases?
Current License: CC BY-SA 4.0
Post Revisions
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 24, 2020 at 9:09 | comment | added | Ross | An example that comes to mind is a developer changing a stored procedure to work with their code which affects other developer as they are working on there own feature branch but all are pointing to the same DB. | |
| Apr 23, 2020 at 21:16 | comment | added | Nathan | In what manner do they step on each other's toes? Change the same entities? Locking queries? | |
| Apr 23, 2020 at 8:48 | answer | added | Robin Bennett | timeline score: 8 | |
| Apr 23, 2020 at 8:22 | review | Close votes | |||
| Apr 29, 2020 at 3:03 | |||||
| Apr 23, 2020 at 8:03 | comment | added | Euphoric | Simply. Don't use production database for development. Create a smaller, sample database for development and testing. Use the production database for performance testing and smoke testing only. | |
| Apr 23, 2020 at 7:57 | review | First posts | |||
| May 7, 2020 at 8:01 | |||||
| Apr 23, 2020 at 7:54 | history | asked | Ross | CC BY-SA 4.0 |