Skip to content

sqlite3: can't run VACUUM on Python 3.6 #73189

Description

@animalize
mannequin
BPO 29003
Nosy @berkerpeksag, @animalize
Superseder
  • bpo-28518: execute("begin immediate") throwing OperationalError
  • Files
  • cannot_vacuum.py
  • Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

    Show more details

    GitHub fields:

    assignee = None
    closed_at = <Date 2016-12-29.15:07:17.995>
    created_at = <Date 2016-12-18.03:19:32.512>
    labels = ['3.7', 'type-bug', 'library']
    title = "sqlite3: can't run VACUUM on Python 3.6"
    updated_at = <Date 2016-12-29.15:07:17.994>
    user = 'https://github.com/animalize'

    bugs.python.org fields:

    activity = <Date 2016-12-29.15:07:17.994>
    actor = 'berker.peksag'
    assignee = 'none'
    closed = True
    closed_date = <Date 2016-12-29.15:07:17.995>
    closer = 'berker.peksag'
    components = ['Library (Lib)']
    creation = <Date 2016-12-18.03:19:32.512>
    creator = 'malin'
    dependencies = []
    files = ['45950']
    hgrepos = []
    issue_num = 29003
    keywords = ['3.6regression']
    message_count = 2.0
    messages = ['283532', '284270']
    nosy_count = 3.0
    nosy_names = ['ghaering', 'berker.peksag', 'malin']
    pr_nums = []
    priority = 'normal'
    resolution = 'duplicate'
    stage = 'resolved'
    status = 'closed'
    superseder = '28518'
    type = 'behavior'
    url = 'https://bugs.python.org/issue29003'
    versions = ['Python 3.6', 'Python 3.7']

    Activity

    1. animalize commented on Dec 18, 2016

      animalizemannequin
      MannequinAuthor

      I'm using Python 3.6.0 RC2.
      When I try to run VACUUM command, an exception raised:

      conn.execute('begin')  # <- remove this line get the same result
      conn.execute('VACUUM')

      sqlite3.OperationalError: cannot VACUUM from within a transaction

      On Python 3.5, everything is fine.
      Attached file cant_vacuum.py is the full example code.

      ----------
      related issue: bpo-10740 sqlite3 module breaks transactions and potentially corrupts data

      R. David Murray said in bpo-10740 about this issue:
      It is an unexpected change in behavior and is therefore probably a bug. It will work if you set isolation_level=None. Because of that I don't think it is a release critical bug, though one could wish we'd discovered it earlier.

    2. added
      stdlibStandard Library Python modules in the Lib/ directory
      type-bugAn unexpected behavior, bug, or error
      on Dec 18, 2016
    3. berkerpeksag commented on Dec 29, 2016

      @berkerpeksag
      Member

      Thanks for trying pre-release versions of Python 3.6, Ma Lin. This has already been reported in bpo-28518 so I'm closing this as a duplicate.

    4. transferred this issue fromon Apr 10, 2022
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

    Metadata

    Metadata

    Assignees

    No one assigned

      Labels

      3.7 (EOL)end of lifestdlibStandard Library Python modules in the Lib/ directorytype-bugAn unexpected behavior, bug, or error

      Projects

      No projects

        Milestone

        No milestone

        Relationships

        None yet

        Development

        No branches or pull requests

        Issue actions