Hey man, if you have any problem, ALWAYS check the django documentation in
the first place. IMO, its preaty extensive and complete, and always helped
me through the 4~5 years I'm developing with django.
After that, stackoverflow always help ( =P ).
And if the things still goes badly, django-users
Hey thanks for that extra input. I'm currently a student at NMSU making an
educational app for NASA'S Planetary Data Systems. Right now I'm the only
student working on it and the only person in my building that knows Django
(which I'm learning on the job). I'm making a blog alongside my app t
Np man, always glad to help!
Just to seal the case, that happened because django dont edit the migration
files itself (well, not through the normal cycle of
"makemigrations">"migrate"). You generated a migration with an invalid
config, and didnt even mattered if you tried to correct that "default
Oh dude you are officially my hero! I didn't even think about the
migration files. That totally worked. And thank you thank you thank you
=D <3.
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiv
Just to clarify:
Change the default value to "False";
Delete the migration file (0012_auto_20170630_1027);
Run makemigrations;
Run migrate.
2017-06-30 15:08 GMT-03:00 Guilherme Leal :
> Have you re-ran the "makemigrations"? If that didnt work, delete the
> migration file (0012_auto_20170630_1027
Have you re-ran the "makemigrations"? If that didnt work, delete the
migration file (0012_auto_20170630_1027) and run "makemigrations" again.
2017-06-30 15:04 GMT-03:00 :
> I also did the "If all else fails, reboot your computer" and still have
> the same problem. Haha. I think I'm screwed.
>
>
I also did the "If all else fails, reboot your computer" and still have the
same problem. Haha. I think I'm screwed.
--
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 ema
Yes. At first I tried setting default=True or default=False for my
BooleanField and kept getting the same error. So I went back in, deleted
the model, tried again, got the same error. Then I deleted my db sqlite3
file, made new migrations, migrated (with the model not even a part of my
model
>>>django.core.exceptions.ValidationError: [u"'' value must be either
True or False."]
Have you tried to set the default value of the BooleanField as True or
False? BooleanFields must have a valid boolean as default value and so
happends that empty string is not a valid boolean.
Change the d
So I made the ultimate error. I put a BooleanField in my models.py, when I
made migrations I set default col value to the empty string ''.. Then I
migrated and got a validation error. However, I have tried to delete the
model containing BooleanField, delete my database file, and I even ran
ma
10 matches
Mail list logo
