Viewing profile — mr_Fatalyst

Thanks, appreciate the support (^_^)!

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_…

One thing that might help here: if you subclass an Oxyde model without defining class Meta: is_table = True, the child class won't be a table and won't have ORM behavior. So you ca…

Right now makemigrations detects add/drop/alter columns, indexes, foreign keys, and constraints. Rename is treated as drop + create, same as Django's default. Automatic rename dete…

[dead]

That's exactly why Oxyde has no lazy loading at all. If you don't call .join() or .prefetch(), related data simply won't be there. N+1 is impossible by design, not by discipline.

Yep, there's a full comparison including SQLAlchemy async: https://oxyde.fatalyst.dev/latest/advanced/benchmarks/

Thanks! Not yet, it's still v0.5 and the API hasn't fully stabilized. But it's getting there.

1. We're all AI agents in a simulation anyway... 2. A converter still means maintaining two model systems. The point was to not have two in the first place. 3. MessagePack overhead…

Well said, that's pretty much how I see it too. Thanks!

Right now it's CLI-based: 'oxyde migrate'. You can call 'apply_migrations()' programmatically, but that's not a publicly documented API yet. Good point though, worth adding.

Thanks! The admin panel supports Quart out of the box, so you should be good to go.

Good question. Working with Python objects in PyO3 requires holding the GIL. With MessagePack, Python serializes to bytes, hands them off, and Rust works completely GIL-free from t…

You can't call filter() without a model. It's always Folder.objects.filter(user_id=user_id), so the context is right there in the code. Plus the generated .pyi stubs give your IDE …

Exactly, that's the idea.

For Oxyde specifically, it's still a young project, so the best public examples I have are the FastAPI tutorial ( https://github.com/mr-fatalyst/fastapi-oxyde-example ) and the adm…

Thanks! Haven't used Prisma much myself, but glad the approach resonates.

Thanks, appreciate it! Felt wrong to ship an ORM without one.

Right, it's not DBAPI compliant. The whole IO stack goes through Rust/sqlx, so PEP-249 doesn't apply. Oxyde has its own exception hierarchy (OxydeError, IntegrityError, NotFoundErr…

Yeah, we're running out of ways to spell oxide (^_^)

Thanks! Not really trying to replace Django ORM though, it's great at what it does. Just trying to build the ORM I'd personally want to use in 2026.

Must have missed that meeting. ORMs are not for everything, but for CRUD-heavy apps with validation they save a lot of boilerplate. And there's always execute_raw() for when you ne…

The Rust core is not just about speed. It bundles native database drivers (sqlx), connection pooling, streaming serialization. It's more about the full IO stack than just making Py…

The ORM doesn't force you to use the DB model as your API schema. It's a regular Pydantic BaseModel, so you can make separate request/response schemas whenever you need to. For sim…

I was surprised too when I saw the results. The benchmarks test standard ORM usage patterns, not the full power of any ORM. SQLAlchemy is more flexible, but that flexibility comes …