django-south

I am trying to add a custom field to my Django project that uses South . Because of this, I am trying (for the first time) to write introspection rules for South . I believe my case is the simplest possible as I am simply extending a CharField. Specifically: class ColorField(models.CharField): def __init__(self, *args, **kwargs): kwargs['max_length'] = 10 super(ColorField, self).__init__(*args, **kwargs) def formfield(self, **kwargs): kwargs['widget'] = ColorPickerWidget return super(ColorField, self).formfield(**kwargs) This is from a Django snippet called jQuery color picker model field for

I have a two models that previously inherited from models.Model and now I've refactored them to inherit from the same base model. Django is using multi-table inheritance for this and I'm trying to generate a schema and data migration for this. There is existing data in the database which needs to be migrated . I know that Django creates a OneToOneField, but I don't understand how it affects existing items in the database. Before Inheritance class BlogPost(models.Model): name = models.CharField() published_on = models.DateTimeField() class AudioFile(models.Model): file = models.FileField()

In the initial stages of my project I'm making a lot of changes to the models and thus I've ended up with a lot of south migrations being generated for my apps. Is it possible to consolidate them in any way before going to my production server to perform the migrations so I don't have like a million migrations for each app? And if so, how would I go about doing that? You could always delete the existing migrations and create a new "initial" migration . To do this, you will need to: Remove the migration files for you app (remove the folder altogether) Run ./manage.py convert_to_south myapp This

I'm creating a schema migration with South 0.7.6 for my Django 1.4.3 project with enabled timezone support. The schema migration includes adding a DateTimeField (with auto_now=True ) on one table. When creating the migration, South prompts me: The field 'MyTable.my_field' does not have a default specified, yet is NOT NULL. Since you are adding this field, you MUST specify a default value to use for existing rows. Would you like to: 1. Quit now, and add a default to the field in models.py 2. Specify a one-off value to use for existing columns now What's the correct one-off value to give here,

I already have a model, class ModelA( models.Model ): name = models.CharField ( max_length = 255, blank = False ) and i have many entries in it. Now i want to add a field in it, which is user = models.OneToOneField( User ) How do i add this field into ModelA ? Is there any solution other than deleting all previous entries? I would use this pattern: Add "user = models.OneToOneField(User, null=True)" to your Model (don't remove the "name" field) run 'manage.py schemamigration --auto'. And apply the migration. Now there are two columns in your table. Now create a datamigration. Edit the file: you

I extended Django admin site for my app to allow non-staff/superusers access. This is working just fine. I created a proxy model for an existing model and registered it to my admin site, however, it doesn't appear for non-staff users. From the documentation I read, my understanding is that proxy models get their own permissions. I checked and these don't appear in the list of available permissions. Here's my code in case it helps: Normal Model class Engagement(models.Model): eng_type = models.CharField(max_length=5) environment = models.CharField(max_length=8) is_scoped = models.BooleanField()

I'm changing a field from CharField to IntegerField . The field name remains the same. The newly created field will be based off the old field. For example, if the old field was "L", it would have the number "1" instead. How can I accomplish this in the forwards() function? The correct way to do it would be to break this into three migrations: A first schema migration to add the new IntegerField field. Followed by a data migration to convert the data originating from the CharField to the IntegerField And a final schema migration to remove the now unused CharField . A fourth one might be

I'm new to django and trying to have a Foreign key back to users for an assignee and reporter. But when i'm trying to apply the change with South i get the error ValueError: The database backend does not accept 0 as a value for AutoField. My Model Code: class Ticket(models.Model): title = models.CharField(max_length=80) text = models.TextField(blank=True) prioritys = models.ForeignKey(Prioritys) ticket_created = models.DateTimeField(auto_now_add=True) ticket_updated = models.DateTimeField(auto_now=True) assignee = models.ForeignKey(User, null=True, related_name='assignee') reporter = models