-
-
Notifications
You must be signed in to change notification settings - Fork 671
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Possibility to change default Pydantic to SQLAlchemy mappings #800
base: main
Are you sure you want to change the base?
Conversation
…nge default mapping. Created PydanticJSONType to store Pydantic models as Json
📝 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 |
See discussion fastapi#761
…nto feature/sa_model_type_mapping
📝 Docs preview for commit fb58b86 at: https://db9f51b8.sqlmodel.pages.dev |
That looks interesting. I'm using Pydantic's 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. |
Hello folks!
First of all i want to apologise for my bad english )
So i want to present two features realised for my project and what i want to share with community:
1)To be allow to change default Python to SqlAlchemy types mapping
2) To be allow to store Pydantic model data as Json at database (with ability to use SQLAlchemy Mutable wrap)
Possible is closes issue #503, but not sure