Maybe Migrations is just really buggy? I am using PostgreSQL as the backend. I added a column with a default value and then did makemigrations then migrate. It doesn't work. I get a very long error.
> On Sep 7, 2014, at 8:54 AM, Malik Rumi <malik.a.r...@gmail.com> wrote: > > Django 1.7rc2 here. Same question, same hope for an answer. It may be that > not all possible changes to a model are intended to be picked up. For > example, I created all my models directly in 1.7rc2, and I have not changed > any fields. What I have done is changed / added some meta and methods. Maybe > these changes don't 'count'? > >> Your models will be scanned and compared to the versions currently contained >> in your migration files, and then a new set of migrations will be written >> out. Make sure to read the output to see what makemigrations thinks you have >> changed - it’s not perfect, and for complex changes it might not be >> detecting what you expect. > > and > >> Migrations are Django’s way of propagating changes you make to your models >> (adding a field, deleting a model, etc.) > > So it might be that unless you change something that actually hits the > database, there won't be anything to migrate, and that makes sense, but it > would be nice if someone with expertise, experience, and inside knowledge > could confirm and explain that. > >> On Tuesday, September 2, 2014 3:16:45 PM UTC-5, David Los wrote: >> Very, very good question. I am experiencing the same issues with Django >> 1.7rc2 and 1.7rc3. >> >> Syncdb and sql statements are intended for Django < 1.7. >> >> Would love to hear a solution! >> >> Op vrijdag 22 augustus 2014 09:32:43 UTC+2 schreef termopro: >>> >>> Hi there, >>> >>> I am using Django 1.7 RC2. >>> I have created models and have run all the migrations so Django created >>> tables in database. >>> Now i decided to change database table names and have added Meta class to >>> models containing table name: >>> >>> class SomeModel(models.Model): >>> ... >>> class Meta: >>> db_table = 'newname' >>> >>> Now when i run "makemigrations" Django doesn't detect any changes in models: >>> "No changes detected in app 'blabla'." >>> As far as i understand the logic, Django should change table names from >>> 'appname_somemodel" to "newname". >>> >>> Is this an expected behavior or i am missing something? > > -- > 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 http://groups.google.com/group/django-users. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-users/c618d499-a1a0-4cbc-953c-0e14bb8f9d59%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- 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 http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/5D1B3515-04E8-46FD-823B-32B64E1B4124%40gmail.com. For more options, visit https://groups.google.com/d/optout.
