Also, your models might reference a setting whose value differs between
development and production. This probably won't cause any problems but will
trip up the migrations autodetector into thinking that a migration needs to
be made.
https://code.djangoproject.com/ticket/24648
On Saturday, Apri
I've run into the problem of migration files not being added to source
control with PyCharm because PyCharm doesn't seem to automatically commit
auto-created files unless you explicitly tell it to in the settings (and
even then it doesn't always work).
--
You received this message because you
Are you sure you are adding your new migrations to your source control? It
sounds like the model changes are being correctly commited but the
generated migrations are not.
On Friday, April 8, 2016 at 11:17:16 AM UTC-5, Neto wrote:
>
> I know, but in production is showing the message that I have
I know, but in production is showing the message that I have to do
makemigrations.
I need a command to know what models need to makemigrations
Em quinta-feira, 7 de abril de 2016 14:50:54 UTC-3, Daniel Roseman escreveu:
>
> You shouldn't ever need to make migrations in production. You make them i
You shouldn't ever need to make migrations in production. You make them in dev,
commit to source control, deploy along with the rest of the code, then run the
migrations in prod.
--
DR.
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsu
In my localhost is everything migrated, but in production have "Run
'manage.py makemigrations' to make new migrations, and then re-run
'manage.py migrate' to apply them."
How to know which models have changed and need make migrations? Exist a
command to know?
6 matches
Mail list logo
