On Sat, Jun 10, 2017 at 5:03 AM, Melvyn Sopacua
wrote:
> On Friday 09 June 2017 20:56:46 James Schneider wrote:
>
>
>
> > Quite honestly this sounds like a bug in the migration system if
>
> > that's the case. I'm pretty sure it should ask what value to use as a
>
> > filler value during the migr
On Friday 09 June 2017 18:08:39 Lee Hinde wrote:
> I'm having problems with a migration after cleaning up an oddity with
> a date field and I'm not sure how to fix it. Any advice appreciated.
>
> I made this change to a date field:
>
> -start_date = models.DateField(db_index=True, default=Fa
On Friday 09 June 2017 20:56:46 James Schneider wrote:
> Quite honestly this sounds like a bug in the migration system
if
> that's the case. I'm pretty sure it should ask what value to
use as a
> filler value during the migration, although I haven't had a
change
> like that in a while.
When yo
On Jun 9, 2017 6:09 PM, "Lee Hinde" wrote:
I'm having problems with a migration after cleaning up an oddity with a
date field and I'm not sure how to fix it. Any advice appreciated.
I made this change to a date field:
-start_date = models.DateField(db_index=True, default=False,
-
I should add, this project is in 1.8.x. I'm working around the problem by
skipping the migration.
--
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 email
to django-users+un
I'm having problems with a migration after cleaning up an oddity with a
date field and I'm not sure how to fix it. Any advice appreciated.
I made this change to a date field:
-start_date = models.DateField(db_index=True, default=False,
- help_text="The date e
6 matches
Mail list logo
