Skip to content

When exporting a database to a file (with default settings and a previous export done), it's not checked if the destination file already exists #835

@Ivan-Perez

Description

@Ivan-Perez

Steps to reproduce this issue

  1. Right click on any table or database.
  2. Click on "Export database as SQL".
  3. Do not configure anything, just click on the "Export" button.
  4. If the output filename already exists, it will be overwritten without warnings.

Default settings I find in this dialog when it opens after Step 2:

imagen

As you see, there's a path in the filename output, probably the last path I entered in that input. No validation occurs to check if the file exists or not.

Current behavior

The file is overwritten without any warning.

Expected behavior

A message box to choose whether overwrite the existing file or not. Something similar to when you save a query tab would be nice.

I've noticed that the check is already performed if you open the file dialog, so this issue only happens when you are saving into the default destination (which I think it's the latest you chose on a previous export).

Possible solution

If that filename is not changed, check if the file already exists and show a message box to allow the user to continue or cancel the operation.

Environment

  • HeidiSQL version: 10.3.0.5794

Metadata

Metadata

Assignees

No one assigned

    Labels

    confirmedIssue verified by project memberenhancementEnhances an existing feature

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions