Keep task length on schedule for backward compatibility

Migrations on existing data would fail because of the old names being longer than the uuid. Keeping the field length at 100 will keep it compatible with existing  data.

Removed the squashed migrations cause this will cause dependency problems on existing installations. Every new migration will list the squashed migrations as a dependency. Not a problem for new installations, but will crash on exisitng ones.

django_q/migrations/0003_auto_20150708_1326.py

@@ -17,10 +17,15 @@ class Migration(migrations.Migration):
         ),
         migrations.AlterModelOptions(
             name='schedule',
-            options={'ordering': ['next_run'], 'verbose_name_plural': 'Scheduled tasks', 'verbose_name': 'Scheduled task'},
+            options={'verbose_name_plural': 'Scheduled tasks', 'ordering': ['next_run'], 'verbose_name': 'Scheduled task'},
         ),
         migrations.AlterModelOptions(
             name='success',
             options={'verbose_name_plural': 'Successful tasks', 'verbose_name': 'Successful task'},
         ),
+        migrations.AlterField(
+            model_name='task',
+            name='id',
+            field=models.CharField(max_length=32, primary_key=True, editable=False, serialize=False),
+        ),
     ]

django_q/models.py

@@ -121,7 +121,7 @@ class Schedule(models.Model):
     schedule_type = models.CharField(max_length=1, choices=TYPE, default=TYPE[0][0], verbose_name=_('Schedule Type'))
     repeats = models.SmallIntegerField(default=-1, verbose_name=_('Repeats'), help_text=_('n = n times, -1 = forever'))
     next_run = models.DateTimeField(verbose_name=_('Next Run'), default=timezone.now, null=True)
-    task = models.CharField(max_length=32, null=True, editable=False)
+    task = models.CharField(max_length=100, null=True, editable=False)
 
     def success(self):
         if self.task and Task.objects.filter(id=self.task):