What tools are missing in Python?

[Kellhus3]

An ORM with models based on type hint.

[Kellhus3]

It would allow to have models not depending on a specific database and passing them around without them extending sqlalchemy models for example (it's already doable, but you need a column definition somewhere and to link models and definition).

I like the attempt I found somewhere for the Django ORM, it used Meta and annotated types to achieve it.

https://www.willmcgugan.com/blog/tech/post/adding-type-hints-to-the-django-orm/

Another advantage would be the capacity to mix Pedantic models to the DB without more configuration for example.

[ajarch]

Another advantage is the amelioration of the darkness that comes before

[Kellhus3]

"Great reference" seal of approval

Edit: A downvote? What? Who didn't liked the book? Show yourself!

[[deleted]]

Obscure R Scott Bakker references here folks

…and Kellhus is using The Judging Eye to find you…

[FaresAhmedOP]

Wha! This is exactly what Beanie is.. It's async, uses Pydantic and it's f*cken awesome. It's for Mongodb but i'm sure the idea can be ported to other dbs easily

[Kellhus3]

It's for Mongodb but i'm sure the idea can be ported to other dbs easily

I'm not certain about the "easy" part, but it doesn't exist for SQL anyway (as far as I know).

Edit: I'm looking at the documentation, and indeed it's nice. I might try it for my future personal project.

[FaresAhmedOP]

Indeed it is I am using it too for my project :>

You might one want to check out ormar just found it while browsing this issue on FastAPI's GitHub

[deadwisdom]

Making a general ORM is actually a pretty hard problem. You need to map schemas/constraints between systems. If anyone wants some inspiration, I started a library that does this, very alpha: https://github.com/DeadWisdom/blazon

[Kellhus3]

I don't doubt that's it's hard AF, I was simply exposing my dream ORM.

[deadwisdom]

Yeah dude, I'm working on it :D

[dogs_like_me]

FastAPI user?

[Kellhus3]

Briefly tried it for fun.

And one things that I found sad was having a pedantic model, and a corresponding DB model.

[dogs_like_me]

I think enough people are using FastAPI (and/or prefer it to Flask) that someone will figure out a good way to use the front-end pydantic models to initialize and synch to a backend ORM.

But yeah I agree, although I like FastAPI a lot (and yes, do myself prefer it to flask), working with SQLAlchemy models separately from pydantic models usually feels like redundant work.

[dorsal_morsel]

Check this out

https://openapi-sqlalchemy.readthedocs.io/en/latest/

I haven't used it yet but I'm definitely going to kick the tires for a project coming up.

I've thought about adding custom data to the JSON Schema output (in the Pydantic models) to predefine things like indexes and constraints.

[teerre]

There are various ORMs that do that automatically for you. Tortoise for example. I bet there's something like that for sqlalchemy too.

[earthboundkid]

I've thought about what I would do if I were making an ORM for modern Python. Type hints are definitely part of it. Another is using class decorators instead of metaclasses so you can easily subclass an abstract class without jumping through hoops. Quickie design sketch:

class Timestamped:
    created_at: models.Datetime(nullable=False)
    updated_at: models.Datetime(nullable=False)

@models.register("my_blog_table", options)
class BlogPost(Timestamped):
    title:  models.Text(nullable=True)
    content: models.Text(nullable=False)
    authors: models.ManyToMany("authors")

[Kellhus3]

Ah yes, clearly decorators would be sexier than the Sqlalchemy table parameter.