calling NamedQuery with update/delete statement instead of select will cause connection not to be returned to pool

[adambezecny]

when calling db.NamedQuery with update/delete statement, e.g.:

query := `INSERT INTO dummy_table(league_id, subscriber_id, messaging_type) 
          VALUES (:league_id, :subscriber_id, :messaging_type)`
if _, err := db.NamedQuery(query, s); err != nil {
      ...
    }

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)?

[Vyacheslav1557]

What about rows.Close() ?