You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, to refer to an existing column in query context, you either:
.set('target',(eb)=>eb.ref('source'))
or:
.set((eb)=>({target: eb.ref('source'),}))
Proposal:
Add setRef to UpdateQueryBuilder to allow:
.setRef('target','source')
and perhaps even:
.setRef({target: 'source',})
...for use cases where all/most values are coming from referenced columns.
We should always look to provide ways not to use ExpressionBuilder if you're only referencing columns - callbacks are expensive at compile-time, and the query becomes less readable and harder to type.
The text was updated successfully, but these errors were encountered:
Hey 👋
Currently, to refer to an existing column in query context, you either:
or:
Proposal:
Add
setRef
toUpdateQueryBuilder
to allow:and perhaps even:
...for use cases where all/most values are coming from referenced columns.
We should always look to provide ways not to use
ExpressionBuilder
if you're only referencing columns - callbacks are expensive at compile-time, and the query becomes less readable and harder to type.The text was updated successfully, but these errors were encountered: