fix migration for request.prof_file field

[dennybiasiolli]

Fixes #244

[albertyw]

Just to confirm, there were no other migration files generated?

[dennybiasiolli]

@albertyw no, this was the only migration file generated by python manage.py makemigration

[xrmx]

@dennybiasiolli thank you sir!

[avelis]

@dennybiasiolli Thanks for making the contribution. Before I approve, would you happen to know if the field will evaluate as an indexable field? I ask because MySQL has a limitation of 191 and we had issues in the past with indexable fields going past max_length of 191. I don't think that is the case here but I wanted to be double sure.

[dennybiasiolli]

@avelis I don't think prof_file will evaluate as indexable field, because in models.py it's defined as

prof_file = FileField(max_length=300, blank=True, storage=silk_storage)

In Class Request the only indexed fields are the following: path, start_time and view_name.

start_time is a DateTimeField, whilst path and view_name have already a max_length=190, so I think there are no problems with MySQL in this case! 😉