Django MySql weirdness

[Steve Bischoff]

http://stackoverflow.com/questions/38534734/django-42000-invalid-default-value-for-action-time

I have been trying to figure this one out for a bit now, does anyone have any tips on why mysql won't take in this date time from django?

Thanks

[Constantine Covtushenko]

Hi Steve,

Can you please provide code snippet here for 'action_time' field?

Regards,

--
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...@googlegroups.com.
To post to this group, send email to django...@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/e7900617-6c13-4bbc-b9ad-a542310d79a8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Steve Bischoff]

https://github.com/django/django/tree/master/django/contrib/admin/migrations

The migrations are in here - the code that is failing in 0002_logentry_remove_auto_add.py

is 

operations = [
	migrations.AlterField(
	model_name='logentry',
	name='action_time',
	field=models.DateTimeField(
	verbose_name='action time',
	default=timezone.now,
	editable=False,
	),
	),
	]