Sep 6, 2026, 6:01 PMPrisma was the gold standard ORM for me for a long time, but the fucked up changes complicating usability and their focus on agent-driven development make me reconsider my approach.
Does anybody know a better JS DB ORM? Little fox is too stupid for SQL.
@finn sadly not really, all I know is sequelize and coming from ActiveRecord and Django ORM, I hated it, super tedious.
Also you are phrasing it wrong, little fox is too smart to suffer with plain SQL :P
Sep 6, 2026, 6:30 PM@crypticcelery I'm reading into sequelize because I have nothing better to do and it doesn't seem too different from Prisma.
What didn't you like about it if I may ask?
@finn compared to others I am used to, it is more for prototypes than production, like just made a basic wrapper around some SQL (better than nothing).
There is no single source of truth for schema & migrations (more like an afterthought, have to define both manually instead of just one), sequelizemm exists but is rather rudimentary.
Also: (1/4)
You have to define relations in both directions, their documented solution (only if you use sync, which you shouldn't) for complex (more than self references) cyclic dependencies is an unacceptable “no foreign key”, I personally dislike the big object style of doing things (why not models as classes with decorated fields and why not chainable reusable queries like e.g. django), model classes don't expose their fields (e.g. why not “include: Book.reviews” (2/4)
@finn
instead of stringly [sic.] typing), …
Upsides:
If it is properly used (I'd put the odds at 30%), typescript's type system would give you one of the best language built-in (no extra LSP/IDE support needed) autocompletions for any ORM (better than django and ActiveRecord). Also, nice use of object keys and symbols for operators (though why not also things like “[Product.review]: {…}” for create with associations). (3/4)
@finn
Maybe take a look at core concepts of SQLAlchemy (amazing ORM featureset, things like recursive queries etc…; needs alembic for migrations though), djangos ORM (especially migration handling and QuerySets), or ActiveRecord (ruby though, so maybe kinda dead). (4/4)
@finn
@finn umm, I hope this wasn't too detailed / too much at once >.<
(my new client does autothreading, look upon my walls of text an despair)