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
Because DbMap.WithContext returns a SqlExecutor (not a DbMap), it is impossible to set the context on a DbMap without transforming it into a SqlExecutor. This becomes problematic when you want to do something like DbMap.Begin, which is only defined on DbMap and not SqlExecutor.
in practice, this means that DbMap.Begin cannot use an existing context, which means it cannot respect deadlines, which is a real bummer when your connection pool is exhausted 😞
at first glance it seems that WithContext oughta return a DbMap; am I misreading something?
The text was updated successfully, but these errors were encountered:
Because
DbMap.WithContext
returns aSqlExecutor
(not aDbMap
), it is impossible to set the context on aDbMap
without transforming it into aSqlExecutor
. This becomes problematic when you want to do something likeDbMap.Begin
, which is only defined onDbMap
and notSqlExecutor
.in practice, this means that
DbMap.Begin
cannot use an existing context, which means it cannot respect deadlines, which is a real bummer when your connection pool is exhausted 😞at first glance it seems that
WithContext
oughta return aDbMap
; am I misreading something?The text was updated successfully, but these errors were encountered: