3 ms·
it's a great solution as long as your queries are no deeper than 2 levels
by ruslan_talpa 9y ago
it's a great solution as long as your queries are no deeper than 2 levels
- jarym 9y agoagreed. If people understand what Join Monster does then they'd see it is still suboptimal in a world where we have Postgres and LATERAL :-D
- lstamour 9y agoHaven’t read enough into lateral joins myself, but if set to pg dialect, join-monster uses lateral joins for pagination: http://join-monster.readthedocs.io/en/stable/dialects/ http://join-monster.readthedocs.io/en/stable/dialects/ I’m sure they’d welcome further feedback or pull requests...
- brdd 9y ago@tylerbainbridge and I work at Conduit (https://conduithq.com https://conduithq.com), where we are using GraphQL, join-monster, and PostgreSQL in production. What you describe isn't a limitation at all-- some of our queries run 10 levels deep and work just fine. In fact, this method is so powerful that most of our queries start from the `user` object and just JOIN off of it.