Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

+1 on that. Handling relationships like parent.child.other_children when writing your own SQL is not trivial at all.


Two join clauses in a statement is not trivial? We apparently have different definitions for "trivial".

But if you want hierarchy (in Postgres), to_jsonb(…) is your friend.


It's much, much slower productivity wise than using the orm. Like 10x slower.

Why TF would I use json? There's a reason I picked a relational database. Nonsense.


It's so nice to use, espacially in a shell.

And also such a performance trap.


Yeah, but once it's a performance issue you're making $$$ and you can add some indexes or write a little SQL in the few places that need it :P


Also child.parents[0].user.username :)




Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: