django-migrations

I want to remove null=True from a TextField: - footer=models.TextField(null=True, blank=True) + footer=models.TextField(blank=True, default='') I created a schema migration: manage.py schemamigration fooapp --auto Since some footer columns contain NULL I get this error if I run the migration: django.db.utils.IntegrityError: column "footer" contains null values I added this to the schema migration: for sender in orm['fooapp.EmailSender'].objects.filter(footer=None): sender.footer='' sender.save() Now I get: django.db.utils.DatabaseError: cannot ALTER TABLE "fooapp_emailsender" because it has

I have a Django application in which I want to change a field from a ForeignKey to a ManyToManyField. I want to preserve my old data. What is the simplest/best process to follow for this? If it matters, I use sqlite3 as my database back-end. If my summary of the problem isn't clear, here is an example. Say I have two models: class Author(models.Model): author = models.CharField(max_length=100) class Book(models.Model): author = models.ForeignKey(Author) title = models.CharField(max_length=100) Say I have a lot of data in my database. Now, I want to change the Book model as follows: class Book

Django 1.7 introduced database migrations . When running the unit tests in Django 1.7, it forces a migrate , that takes a long time. So I would like to skip the django migrations, and create the database in the final state. I know that ignoring the migrations can be a bad practice, as that part of the code would not be tested. But that's not the case: I'm running the full migrations in the CI test server (jenkins). I only want to skip the migrations in my local tests, where the speed matters. Some context: Until Django 1.6 , when using South, I used the SOUTH_TESTS_MIGRATE setting: By default,

The documentation for Django 1.7 mentions RunSQL classes can be used to create partial indexes on your tables. I have a table where I want the combination of title , blog & category to be unique. However if category is not provided, the combination of title & blog should still be unique. class Post(models.Model): title = models.CharField(max_length=200) blog = models.ForeignKey(Blog) category = models.ForeignKey(Category, null=True, blank=True) I can achieve this constraint with partial indexes (like the SQL shown below). Where do I add this code if I'm using Django 1.7 migrations? CREATE

I've been a user of Django for about 2 years now and there is a feature I have always been afraid of using : faking migrations . I've looked pretty much everywhere and the most information I can get is from the documentation where it states that: --fake Tells Django to mark the migrations as having been applied or unapplied, but without actually running the SQL to change your database schema. This is intended for advanced users to manipulate the current migration state directly if they’re manually applying changes; be warned that using --fake runs the risk of putting the migration state table

i'd like to use a view i've created in my database as the source for my django-view. Is this possible, without using custom sql? ******13/02/09 UPDATE*********** Like many of the answers suggest, you can just make your own view in the database and then use it within the API by defining it in models.py. some warning though: manage.py syncdb will not work anymore the view need the same thing at the start of its name as all the other models(tables) e.g if your app is called "thing" then your view will need to be called thing_$viewname Since Django 1.1, you can use Options.managed for that. For