Re:Show HN: Oxyde – Pydantic-native async ORM with a Rust core
by mr_Fatalyst on Tuesday March 17, 2026 @12:25PM
(#47414860)
The way I see it, having everything as Pydantic makes this natural. Your DB model, your request schema, your response DTO are all BaseModels. Converting between them is just model_dump() and model_validate(), or plain inheritance. No adapters, no mapping layers. So when you need to split things apart, it's straightforward rather than painful.
[ Parent
| on HN ]
Re:Show HN: Oxyde – Pydantic-native async ORM with a Rust core
by globular-toast on Wednesday March 18, 2026 @09:43AM
(#47425732)
Yeah, but I'm afraid of a system like Django where not calling `.save()` in the wrong place is down to discipline and understanding. I want there to be some way to stop this happening that doesn't rely on a couple of maintainers keeping strict vigilance over the codebase.