Closed itinneed2022 closed 1 year ago
This database was originally on an older version of django. When I ran the migrations the first time, they did not upgrade the database and permit the last_login column to permit null. I couldn't find a way to fix this with Django so I had to update the database directly with: ALTER TABLE auth_user modify last_login datetime null;
Sorry, Django migrations are complicated and unfortunately, out of scope, of Graphite itself. But if fixing outside of Django worked - that's also an solution.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
I'm getting this error for new users on my prod graphite setup:
Oddly, this isn't happening in my dev setup which is the exact same version of django, graphite-web, etc.
Googling for an answer I found some posts saying a migration of django was necessary. Is there a migration option to set the last login field to accept "null"?
Version info: asgiref==3.4.1 attrs==21.4.0 Automat==20.2.0 cairocffi==1.2.0 cffi==1.15.0 charset-normalizer==2.0.12 constantly==15.1.0 cryptography==37.0.2 Django==2.1 django-tagging==0.4.6 hyperlink==21.0.0 idna==3.3 incremental==21.3.0 pycparser==2.21 PyMySQL==1.0.2 pyparsing==3.0.9 python-memcached==1.59 pytz==2022.1 six==1.16.0 sqlparse==0.4.2 Twisted==22.4.0 txAMQP==0.8.0 typing_extensions==4.1.1 urllib3==1.26.9 whisper==1.2.0 whitenoise==4.1.4 zope.interface==5.4.0