Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • G go
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Kirill Smelkov
  • go
  • Repository
  • go
  • src
  • database
  • sql
  • sql.go
Find file BlameHistoryPermalink
  • Chris Hines's avatar
    database/sql: close bad connections in commit or rollback: · d737639c
    Chris Hines authored Aug 24, 2015
    Previously Tx.close always passed a nil error to tx.db.putConn. As a
    result bad connections were reused, even if the driver returned
    driver.ErrBadConn. Adding an err parameter to Tx.close allows it to
    receive the driver error from Tx.Commit and Tx.Rollback and pass it
    to tx.db.putConn.
    
    Fixes #11264
    
    Change-Id: I142b6b2509fa8d714bbc135cef7281a40803b3b8
    Reviewed-on: https://go-review.googlesource.com/13912
    
    
    Reviewed-by: default avatarBrad Fitzpatrick <bradfitz@golang.org>
    Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org>
    TryBot-Result: Gobot Gobot <gobot@golang.org>
    d737639c
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7