Closed 4bo closed 3 years ago
Thanks! There's no urgency on this, but nevertheles, I'd be happy to take a MR to fix it.
It should probably be an AutoField, rather than a BigAutoField, to avoid having to perform potentially massive migrations.
On Sun, 5 Sept 2021 at 10:31, 4bo @.***> wrote:
running manage.py migrate i got this warning:
app_1 | Running migrations: app_1 | Applying watson.0001_initial...System check identified some issues: app_1 | app_1 | WARNINGS: app_1 | watson.SearchEntry: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. app_1 | HINT: Configure the DEFAULT_AUTO_FIELD setting or the AppConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/etianen/django-watson/issues/285, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABEKCD5CSPQOFI5KOYFEIDUAM2G5ANCNFSM5DOT6NRQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
running
manage.py migrate
i got this warning: