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
You need to sign in or sign up before continuing.
  • go
  • src
  • database
  • sql
  • sql.go
Find file BlameHistoryPermalink
  • Justin Li's avatar
    database/sql: document Stmt lifetime · d5a36531
    Justin Li authored Jan 23, 2019
    When prepared on a DB, prepared statement code in database/sql handles everything to keep the prepared statement alive as it moves across the connection pool. Understanding this is an important part of using this API correctly, but it was only documented indirectly via `(*Tx) Prepare*`.
    
    Change-Id: Ic8757e0150d59e675d9f0252f6c15aef2cc2e831
    GitHub-Last-Rev: 55dba87458542cb631baac80aeea0c3607d8f421
    GitHub-Pull-Request: golang/go#29890
    Reviewed-on: https://go-review.googlesource.com/c/159077
    
    
    Reviewed-by: default avatarBrad Fitzpatrick <bradfitz@golang.org>
    Reviewed-by: default avatarDaniel Theophanes <kardianos@gmail.com>
    d5a36531
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7