4 ms·
I haven't used Django ORM before but it would be interesting to see how Peewee compares to SQLAlchemy: http://www.sqlalchemy.org/ http://www.sqlalchemy.org/ I
by julian37 16y ago
I haven't used Django ORM before but it would be interesting to see how Peewee compares to SQLAlchemy: http://www.sqlalchemy.org/ http://www.sqlalchemy.org/
I love SQLAlchemy: it is easy to use, rock solid, well documented, and fully-featured without trying to do everything at once (for example, it explicitly doesn't do caching).
The author and principal maintainer, Michael Bayer, does a fantastic job developing the project at a sensible pace and answering any questions on the mailing list quickly and patiently.
It is hands down one of the most well-run open source projects that I know of, and a fantastic ORM.
Again, it would be interesting to see how Peewee stacks up against it (performance-wise, since it obviously doesn't compete for features.)
- bobbyi 16y agoMichael Bayer's other project, the Mako templating system, is excellent as well http://www.makotemplates.org/ http://www.makotemplates.org/
- deleted 16y ago[deleted]
- zzzeek 16y agoA tiny one-file ORM (I checked, the full ORM itself is ultimately one file "peewee.py") like Peewee that loads objects with a super-shallow stack depth will have very low method call overhead for the things it does do, and in Python method calls are everything. So an ORM like SQLA will appear slower on simplistic benches which compare database sequences on a near one-to-one basis. Where we try to be the most performant in the real world is that we try to make it extremely easy to cut down the number of SQL calls in a complex graph dramatically via collections, eager loading, stateful sessions, delayed flush, etc.
- coleifer 16y agoYou couldn't be more correct.