If you want to create a different URL for Django's Admin while keeping /admin/ intact:
Create an instance using `from django.contrib.admin import AdminSite` and `site = AdminSite(name='staff')`.
If you encounter the django.db.utils.InterfaceError: "(0, '')" error
When this error occurs intermittently during get operations depending on the table or record, it might be due to a mismatch in the connection character encoding.
If a Django project that has been working until now fails to start after a long time with the following error:
```
version_info, _mysql.version_info, _mysql.__file__
NameError: name '_mysql' is not defined
```
When running `python3 ./manage.py runserver 8080`, I encountered the error `django.db.utils.OperationalError: (2000, 'Unknown MySQL error')`. This error occurs when the `OPTIONS` setting includes `'charset': 'utf8mb4'`.
MySQL raises error 1467 'Failed to read auto-increment value from storage engine' when a Django int id hits the AUTO_INCREMENT limit 2147483647. Check information_schema, then migrate the primary key to BigAutoField.
Fix `from_db_value() missing 1 required positional argument: 'context'` on custom Django fields after upgrading to Django 3 — adapt to the removed `context` arg.
When developing with Vue, if you are running a webpack dev server and using Django for the API backend along with Django's authentication using Python social auth and an external Auth provider, you may encounter an issue.
Avoid `table already exists` failures in Django tests when running with `--keepdb` after cancelling migrations — how to forcibly reset the test DB migration state.
Django: Best way to unit-test an abstract model - Stack Overflowhttps://stackoverflow.com/questions/4281670/django-best-way-to-unit-test-an-abstract-model
When using Django, setting `Meta: managed = False` in a model can sometimes lead to a `ProgrammingError` during unit tests from other apps when attempting operations such as `create()`. This is a memo on how to address this issue.
When I tried to migrate a project using Python 2.7 + Django 1.6 to Python 3.5 + Django 2.0 and recreated the migration files, running ./manage.py migrate resulted in the following error: