Re: How to know which models have changed and need make migrations?
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, April 9, 2016 at 9:52:27 AM UTC-4, jorr...@gmail.com wrote: > > 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 subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/eed606ed-0f95-4c23-8210-035ebc028998%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: How to know which models have changed and need make migrations?
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 subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/56c2a5e2-af13-44d5-82b6-db769c2c5861%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: How to know which models have changed and need make migrations?
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 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 >> 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 unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/19f7a27a-c81c-492e-b2f2-6ecc531672f5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: How to know which models have changed and need make migrations?
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 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 unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/547338e9-71c7-455f-9acb-75d622077246%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
How to know which models have changed and need make migrations?
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 unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/4054850c-1830-4b74-831a-1ac34fa213a1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
How to know which models have changed and need make migrations?
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? -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/2902f9a3-e7f6-43cb-b920-eb735f7e288f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
