4 ms·
I love your syntax for joins and unions! A bit puzzled by why the connector slots into the query, instead of the query slotting into the connector, given that
by Eric_WVGG 2y ago
I love your syntax for joins and unions!
A bit puzzled by why the connector slots into the query, instead of the query slotting into the connector, given that it’s the connector that’s actually doing the work. I.e.
‘connector.fetch(query)‘
… rather than…
‘query.fetch(connector)‘
- tilyupo 2y agoIt was more of an ergonomics choice. To me it seems like it's more readable to write `await users.filter(user => user.id.eq(42).fetch(connector)` instead of `await connector.fetch(users.filter(user => user.id.eq(42))`. But I might be wrong, your idea makes more sense from logical perspective.
- deleted 2y ago[deleted]
- jgoyvaerts 2y agoWhat about moving the connector to the table declaration, similar to dbcontext in .net? Something like Q.table(definition, connector), which would then allow you to just write users.filter(user => user.id.eq(42).fetch()
- williamdclt 2y agoI’m not sure I can say which is _objectively_ better, but I was also surprised, connector.fetch would be more consistent with common JS practices