📝 Docs preview for commit 6b5f287 at: https://6b70ec7d.sqlmodel.pages.dev

Looks like in new version of pydantic (2.6.1) added some breaking changes. All completed tests at MR pipeline was started with previous stable version of pydantic - 2.5.3

This commit at Pydantic.main totally breaks the eq behaviour

pydantic/pydantic@62ed0aa#diff-8708af8d26c26644976866f974e0b810b0940ede43ff487e457057d5a1f07999

See discussion about _eq at #761

📝 Docs preview for commit fb58b86 at: https://db9f51b8.sqlmodel.pages.dev

That looks interesting. I'm using Pydantic's NaiveDatetime, and since it isn't a subclass of datetime.datetime I have to pass sa_type=saDateTime (from sqlalchemy import DateTime as saDateTime) on every field. Otherwise get_sqlalchemy_type() wouldn't know how to handle this type in the database.

However I think this case should be handled internally by SQLModel and without requiring extra code since SQLModel already depends on Pydantic and could just as well support these types.

This pull request has a merge conflict that needs to be resolved.

@sambadi, thanks for implementing this! I considered doing it myself one day, but now I don't have to. ❤️
Could you please rebase the branch and resolve the conflicts so we can move on easier?

@sambadi, thanks for implementing this! I considered doing it myself one day, but now I don't have to. ❤️ Could you please rebase the branch and resolve the conflicts so we can move on easier?

I'll try, but not sure that can find enough time =(

Hey everyone!

I am looking for this feature without have to monkeypatch as in my comment referred to this PR (#1967 #503), so I fork the branch and update it to the last changes, you can see it in fbuccioni/sqlmodel:sa_model_type_mapping I try submitting the PR to the original author @sambadi in the following PR but haven't answer so I post it in the original PR, tell me if something additional is needed.

Thanks in advance