Skip to content

bug: safe mode edits don't apply when connection already opened #357

@eliottwantz

Description

@eliottwantz

What happened?

When I change the safe mode in an opened database connection, the changes are not reflected, and the initial safe mode level set in the database connection details are the ones that gets applied

Steps to reproduce

  1. Open a connection in safe mode to full
  2. Run a query, the safe mode works and alerts with password for confirmation.
  3. Go to the top, and change the safe mode to silent
  4. Run a query, it is still treated as safe mode full, and shows the popup confirmation with password required.

Expected behavior

Changes to safe mode in an opened connection are persisted for the duration of the connection

Database type

None

TablePro version

0.20.1

macOS version & chip

macOS 26.3.1 / Apple Silicon

Screenshots / Logs

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions