Adjust test when inserting non-nullable email field

[stephane]

Without this workaround, the test raises an Pydantic error:

tests/test_fastapi_users_db_sqlalchemy.py:110: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

>   ???
E   pydantic.error_wrappers.ValidationError: 1 validation error for UserDB
E   email
E     value is not a valid email address (type=value_error.email)

pydantic/main.py:406: ValidationError

My env uses pydantic==1.8.2 (same version as the CI so I don't know why the behavior is different for me).

[frankie567]

Never paid attention to that but, indeed, Pydantic should definitely raise an error first 🤔 Will try to investigate why it works on my machine and CI ; because yes, it shouldn't work 😅

[frankie567]

Ok, so I've run again the tests in CI and local machine and getting the same error now; which is expected. Actually, I've reworked the base models in the base library some time ago and didn't update the database libraries accordingly.

I'll update every projects with the .construct syntax of Pydantic, so I won't keep your proposal, but you definitely raised an important point here. Thank you 🙏

[stephane]

Thank you for your review. 👍