Timeline for Managing a development database in a group project
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 19, 2016 at 7:07 | vote | accept | Audite Marlow | ||
| Mar 20, 2016 at 17:27 | answer | added | Doc Brown | timeline score: 2 | |
| Mar 18, 2016 at 14:17 | comment | added | Audite Marlow | @DocBrown: Thanks for the heads up on the cross post thing, I was not aware of this. I will have a look at Laravel's database seeding and discuss it with my team. | |
| Mar 18, 2016 at 12:30 | comment | added | Doc Brown | .. and FWIW: this former SO post might give you a hint (just think of your development test data as production data). | |
| Mar 18, 2016 at 11:28 | comment | added | Audite Marlow | @DocBrown: Currently we don't have a production database since we haven't even started developing yet. The point of my question is to figure out what our best options are. As for other projects, we just manually update the production database with tools such as PHPMyAdmin. | |
| Mar 18, 2016 at 10:58 | comment | added | Doc Brown | @AuditeMarlow: I do not understand how this answers my questions. Your production database has some data. Laravel's migrations would delete the data, so you do not use that mechanism for the production database when you want to deploy a schema change, I guess. So which mechanism do you use for the production DB. Handwritten SQL scripts? (And please, address me with the @ sign, otherwise I do not see you answers in my inbox). | |
| Mar 18, 2016 at 10:52 | comment | added | Audite Marlow | Say I have a production database and a development database. Something changes in the development database, thus it also has to change (eventually) in the production database. I cannot afford to start clean with the production database. | |
| Mar 18, 2016 at 10:25 | comment | added | Doc Brown | How do you handle db migrations in production? You surely do not throw away the old data every time you create a new production release. So why not use the same mechanism for development? | |
| Mar 18, 2016 at 9:18 | comment | added | Derek Elkins left SE | Why not "refill" your database every time? For the purposes of development and testing, you should have the creation of test data scripted out. These scripts should be able to complete in seconds even for fairly large amounts of data. | |
| Mar 18, 2016 at 8:33 | history | asked | Audite Marlow | CC BY-SA 3.0 |