Welcome Guest, Not a member yet? Register   Sign In
Automatic Database Migrations - Proposal

Hello community, 
i had a few projects in Python/DJANGO and have seen some really useful stuff but one especially helpful

Database migrations generated automatically from the Models

i love CI and want to have all the good stuff in here as well to speed up development times


- table field definitions are in a single place (single source of truth) in the Model
- migration files are temporary
- you can delete all dev incremental migrations and recreate a final migration

i understand that this is a braking change for the CI updates but that's why i ask your opinions on this.

we already have the $allowedFields property defining the field names

i propose new property called $fields or similar describing the fields like in the migrations currently, this also needs clarification.

What are your thoughts ?

I have a module that plans to include this:


The Publisher handlers aren’t written yet but the Model Drafter is there. I have to peel for another project but hopefully will be looking at Publisher soon.

Thanks @MGatner but from what i saw your library is doing schema generation from existing Database.
what i would like to have or make is

Model ----> migrations ----> database <---- Seeds (fixtures)

so that the schema definition is in one place and thats the Model

whats your recommendation for this, i understand that you have lots of experience on this already and i don't want to reinvent the wheel.

Yep. I understood, and it is planned but not coded yet.

Theme © iAndrew 2016 - Forum software by © MyBB