Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
shibahug shibahug
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 5
    • Issues 5
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Lartu
  • shibahugshibahug
  • Issues
  • #2

Closed
Open
Created Sep 10, 2018 by Lartu@lartu🐕Maintainer

No way to know amount of affected rows in update/delete

Created by: mdg92

There is no way to know the amount of affected rows by update and delete queries. Not having the ability to lock the table, the sqlCount is not enough, since the value could have changed between statements. Could be solved with #1 if second choice is used.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking