byro "Migrate" warnings

[spaetz]

Hi, I have been installing byro 0.0.2 (current git) and it seems to run fine. Thanks! When issueing "./manage.py migrate" I get a bunch of warnings from django though, which perhaps should be solved. I am not deep enough in the code yet, to provide a merge request, but will be happy to provide one, if the fix is as trivial as the HINT suggests.

bookkeeping.Account: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'.
	HINT: Configure the DEFAULT_AUTO_FIELD setting or the BookkeepingConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'.

	HINT: Configure the DEFAULT_AUTO_FIELD setting or the CommonConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'.
common.LogEntry: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'.

	HINT: Configure the DEFAULT_AUTO_FIELD setting or the DocumentsConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'.
mails.EMail: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'.

	HINT: Configure the DEFAULT_AUTO_FIELD setting or the MailsConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'.
mails.MailTemplate: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'.

[spaetz]

P.S. and I have not yet found out when it is being logged, but after a "manage.py" migrate & createsuperuse & makemessages --all, my log contains:

    return self.cursor.execute(sql, params)
  File "/var/www/vhosts/hosting169198.ae858.netcup.net/httpdocs/ff2931.sspaeth.de/lib/lib/python3.7/site-packages/django/db/utils.py", line 90, in __exit__
    raise dj_exc_value.with_traceback(traceback) from exc_value
  File "/var/www/vhosts/hosting169198.ae858.netcup.net/httpdocs/ff2931.sspaeth.de/lib/lib/python3.7/site-packages/django/db/backends/utils.py", line 84, in _execute
    return self.cursor.execute(sql, params)
  File "/var/www/vhosts/hosting169198.ae858.netcup.net/httpdocs/ff2931.sspaeth.de/lib/lib/python3.7/site-packages/django/db/backends/sqlite3/base.py", line 423, in execute
    return Database.Cursor.execute(self, query, params)
django.db.utils.OperationalError: no such table: common_configuration

But that is certainly a different issue.

[rixx]

Please open separate issues for separate problems! Though your last one sounds like you haven't executed all migrations, or not successfully, or are connected to a different db/different environment.

[rixx]

There really isn't any need to do anything, as the log entries you saw are not errors, just notices that django is assuming a well-defined default value. But I'll push a change to avoid future confusion.