Cansin Yildiz

Setting the field type explicitly such as: ```py import graphene from graphene_django import DjangoObjectType GenderType = graphene.Enum.from_enum(Person.Gender) class PersonType(DjangoObjectType): class Meta: model = Person use_connection = True gender = GenderType()...

I have realized, introducing `null=True, default=None` to the `CharField` fixes the issue. But that is against the best practices described by Django's documentation per https://docs.djangoproject.com/en/3.0/ref/models/fields/#null . But at least we...

I am dealing with the exact same issue. Looks like there was a fix merged into the master. As @ThiefMaster was pointing out, @gabrielfalcao would it be possible to deploy...

Here is a sample error: `pytest.ini` ``` [pytest] addopts = --cov=hyke --cov-report=html --cov-report=term --cov-report=xml --failed-first --no-cov-on-fail --numprocesses=auto --reuse-db ``` bash ``` pipenv run pytest --create-db ============================= test session starts ==============================...

I think `pytest-django` needs a logic that would make sure the database is created for the first connection, and the other processes just shared a connection to that DB, similar...

And that logic needs to be implemented at https://github.com/pytest-dev/pytest-django/blob/master/pytest_django/fixtures.py#L101

To be clear, I am referring to the code section within `if parallel > 1:`. Just a theory though.

Actually no. I guess you are already doing it manually in your code at `django_db_modify_db_settings_xdist_suffix`. Hmm 😕

I guess the default Django-test runner's parallel option does not even allow re-using the same DB on different processes.

I wonder what @blueyed and @adamantike think.