Hey Abraham,
to be more specific, when you used South and ran "manage.py
datamigration" [1] you got an empty migration file with a forwards and
backwards method where you had to fill out the blanks and tell South
what to do, e.g. to create a certain object in the database.
With Django's migration
On Wed, Jan 14, 2015 at 6:34 AM, Abraham Varricatt <
abraham.varric...@googlemail.com> wrote:
To be more specific, the document you link clearly mentions that "Django
> can’t automatically generate data migrations for you"
>
>
> And this is what puzzles me. If it isn't automated and is something t
To be more specific, the document you link clearly mentions that "Django
can’t automatically generate data migrations for you"
And this is what puzzles me. If it isn't automated and is something that
needs to be done manually, what's so great about it's inclusion in Django
1.7?
Slowly discover
On Wed, Jan 14, 2015 at 3:03 PM, Abraham Varricatt <
abraham.varric...@googlemail.com> wrote:
> Hello everyone,
>
> One of the biggest features introduced in Django 1.7 are migrations. They
> can broadly be classified into 2 types -
> * schema migrations
> * data migrations
>
> Schema migrations d
Hello everyone,
One of the biggest features introduced in Django 1.7 are migrations. They
can broadly be classified into 2 types -
* schema migrations
* data migrations
Schema migrations deal with changes to the database schema. eg - changing
max_digits of a DecimalField.
Data migrations revol
5 matches
Mail list logo