3 ms·
For a decade I avoided sqlalchemy, we finally got to use it last year and found it quite overwhelmingly complex and 1.4 documentation is messy. We had to use mi
by v3ss0n 4y ago
For a decade I avoided sqlalchemy, we finally got to use it last year and found it quite overwhelmingly complex and 1.4 documentation is messy. We had to use mixed styles.
I checked unified doc and it had improved but , still wall of texts.. quite hard to read.
Readability count's.
- whoopdeepoo 4y agoWhat do you use instead?
- v3ss0n 4y agoNow we're using Django for current project. But for new project we planned to use Starlite framework so we are still deciding 1. PicoloORM 2. Sqlalchemy 2.x And now finding sqlalchemy 2.0 still way too complicated
- gkmcd 4y agoHave you looked at peewee? It might be just what you're looking for. http://docs.peewee-orm.com/ http://docs.peewee-orm.com/
- thisismyswamp 4y agoAbsolutely agree, coming from the Node.js world documentation for Python packages (especially more established ones) is largely unapproachable, wording is unnecessarily obtuse and descriptions go on for too long. Code is presented in walls instead of being elegantly interspersed with short descriptions.