`Optional[str]` triggers `int_parsing` instead of string parsing when used for `odmantic.Model` about odmantic HOT 4 CLOSED

Might be related to pydantic/pydantic#8362
Edit: it is

from odmantic.

because of the new_root hack in validate_type (it aliases all field types), this problem pops up for any Model with more than 1 Union/Optional field.

from odmantic.

oh wow... I had this with an Optional[datetime] field and thought it was probably because PyMongo already fetched mongo Date as Python datetime and then Pydantic was expecting to deserialize JSON. I was wondering if maybe odmantic can only read data that it wrote itself (i.e. if it was inserting dates as strings to the db)

but it seems like it's actually just this bug, as I also had a couple of Optional[str] fields on the model... and either removing them or making my date field non-optional allows to parse a row successfully (but then the model is no longer usable for my app)

this fix here #416 works for me 👍

from odmantic.

Yes, this is fixed by #416. Amazing job @netomi!

from odmantic.