Re: Changes to Model does not migrate to sqlite with Django 1.7?

2014-12-10 Thread Collin Anderson
Hi, Storing your files in dropbox _should_ be fine, unless it's a problem with *.pyc or __pycache__ files. Collin On Tuesday, December 9, 2014 2:38:31 PM UTC-5, Tobias Dacoir wrote: > > Hi, > > I'm afraid I don't have them. Apparently after deleting my database file > and then just running man

Re: Changes to Model does not migrate to sqlite with Django 1.7?

2014-12-09 Thread Tobias Dacoir
Hi, I'm afraid I don't have them. Apparently after deleting my database file and then just running manage.py makemigrations, it deleted the old migration files and started anew. Right now I'm also unable to re-produce it on purpose :( But it happened a couple of times for me since I regularly

Re: Changes to Model does not migrate to sqlite with Django 1.7?

2014-12-09 Thread Tobias Dacoir
Yes of course. Like I said, when I run into this error I have to delete my database file and do a fresh migration anyway. -- 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

Re: Changes to Model does not migrate to sqlite with Django 1.7?

2014-12-09 Thread Collin Anderson
Hi, Another silly question: have you made the initial migration(s) for your app yet? Collin On Monday, December 8, 2014 6:07:11 AM UTC-5, Tobias Dacoir wrote: > > Ok, here is part of the User Model: > > class User(AbstractBaseUser, PermissionsMixin): > > SEX = ( > ('m', 'male'), >

Re: Changes to Model does not migrate to sqlite with Django 1.7?

2014-12-08 Thread Daniel Roseman
On Monday, 8 December 2014 11:07:11 UTC, Tobias Dacoir wrote: > So what am I doing wrong? I'm sure it's just my fault. At first I even > manually edited the migrations file in the past, for example when I changed > one of the fields to be mandatory instead of being optional. Old data in > the

Re: Changes to Model does not migrate to sqlite with Django 1.7?

2014-12-08 Thread Markus Holtermann
I tried to reproduce the problem with the steps you explained, but it works fine for me. Can you post your existing migration files for that app too, please. This will then hopefully give us some hints to solve your problem. On Monday, December 8, 2014 12:07:11 PM UTC+1, Tobias Dacoir wrote: > >

Re: Changes to Model does not migrate to sqlite with Django 1.7?

2014-12-08 Thread Tobias Dacoir
Well, I did follow some best-practice guides and even asked here on the forums on how to model my User class. I want the users to be able to use their username or email as login, and going with this inheriting from AbstractBaseUser and PermissionsMixin is what I was told. Maybe this doesn't wor

Re: Changes to Model does not migrate to sqlite with Django 1.7?

2014-12-08 Thread Markus Holtermann
A model is always uniquely identified by its app label and model name. Since migrations use that I don't see a way how this could happen. If you have two apps with the same app label the AppRegistry will blow up (and prevents Django from starting). On Monday, December 8, 2014 12:15:30 PM UTC+1,

Re: Changes to Model does not migrate to sqlite with Django 1.7?

2014-12-08 Thread James Schneider
You can also temporarily remove django.contrib.auth from INSTALLED_APPS when making your migrations to keep the overlap from occurring as a test, although I'm not sure if that would be possible if any other code references the contrib User model and probably isn't recommended as a production deploy

Re: Changes to Model does not migrate to sqlite with Django 1.7?

2014-12-08 Thread James Schneider
I have to wonder if the name of your class is causing an overlap with the Django contrib model, which may be causing confusion with the migrations process and not catching changes (since the core contrib version doesn't have any changes). Would it be possible to change the name of the class, even

Re: Changes to Model does not migrate to sqlite with Django 1.7?

2014-12-08 Thread Tobias Dacoir
Ok, here is part of the User Model: class User(AbstractBaseUser, PermissionsMixin): SEX = ( ('m', 'male'), ('f', 'female') ) RANG = ( ('b', 'beginner'), ('e', 'expert'), ('m', 'master') ) username = models.CharField(_('username'), max_

Re: Changes to Model does not migrate to sqlite with Django 1.7?

2014-12-08 Thread Markus Holtermann
Hi Tobias, can you share the code for your old model and you new model along with the existing migrations for that app, please. Without some details it's hard to figure out what's happening. /Markus On Monday, December 8, 2014 8:23:33 AM UTC+1, Tobias Dacoir wrote: > > Hi, > > I'm having troub

Re: Changes to Model does not migrate to sqlite with Django 1.7?

2014-12-08 Thread Daniel Roseman
On Monday, 8 December 2014 07:23:33 UTC, Tobias Dacoir wrote: > > Hi, > > I'm having trouble with changes to my Models. I just added a couple of new > fields to my existing models but when I run manage makemigrations it says: > No changes detected. When I try to log in to the admin panel it gives

Changes to Model does not migrate to sqlite with Django 1.7?

2014-12-07 Thread Tobias Dacoir
Hi, I'm having trouble with changes to my Models. I just added a couple of new fields to my existing models but when I run manage makemigrations it says: No changes detected. When I try to log in to the admin panel it gives an operational error and says: No such column (because I added a column