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
connection is not returned into pool leading ultimately to pool exhaustion. The correct way is to call db.NamedExec instead. The problem is API is not preventing one from calling inappropriate method (NamedQuery) with update/delete. This leads to very tricky and hard to troubleshoot errors. Could this be documented in method comments and ideally somehow prevented in runtime (e.g. trowing fatal error when calling NamedQuery with update/delete)?
The text was updated successfully, but these errors were encountered:
when calling db.NamedQuery with update/delete statement, e.g.:
connection is not returned into pool leading ultimately to pool exhaustion. The correct way is to call db.NamedExec instead. The problem is API is not preventing one from calling inappropriate method (NamedQuery) with update/delete. This leads to very tricky and hard to troubleshoot errors. Could this be documented in method comments and ideally somehow prevented in runtime (e.g. trowing fatal error when calling NamedQuery with update/delete)?
The text was updated successfully, but these errors were encountered: