Django 1.7 built in migrations vs South migrations? -

Django 1.7 built in migrations vs South migrations? -

i have checked issue in questions , couldn't found simple explanation django build in migrations or - reliable plenty ?

i started new project django 1.7 , facing lot of problems build in migrations. simple things normal in south raise me exception in version. illustration changing charfield foreignkey raise error cannot cast field type int, normal , that's why making migration. know things had create south in previous projects uncertainty django migrations handle such operations ? illustration custom fields introspections, converting foreign key manytomany,abstract classes alter fields, , many others ... question is:

are django 1.7 build in migrations reliable plenty big complicated normalized database construction ?

p.s. @ to the lowest degree powerfull south(if problem in utilize of them handle it, don't want fall in situation project ready, database has lot of records , have alter requires table deletions , other risky operations).

you have know django core migrations has been written andrew godwin, main contributor of south.

and words were:

"south's four-year-old design hitting serious limits, it's time add together migration back upwards django itself"

so, understand django core migration not "parralel" migration system, new one, , supposed improve one. don't know south well, if you're facing errors core migrations, because not work same way south, , things need accomplish in different way. don't think it's because new tool not reliable.

of course, new tool, have careful bugs (go update 1.7.1) django extensively tested , stable framework.

django django-migrations