Skip to content

Fix #20160 - Skip tables that cannot be read in SQL structure export - #20379

Open
eyupcanakman wants to merge 1 commit into
phpmyadmin:QA_5_2from
eyupcanakman:fix/export-sql-skip-unreadable-table
Open

Fix #20160 - Skip tables that cannot be read in SQL structure export#20379
eyupcanakman wants to merge 1 commit into
phpmyadmin:QA_5_2from
eyupcanakman:fix/export-sql-skip-unreadable-table

Conversation

@eyupcanakman

Copy link
Copy Markdown
Contributor

Description

When a single table cannot be read (for example an InnoDB table on a server started with skip-innodb), the whole SQL export failed with an Error reading structure for table error instead of exporting the readable tables. The export loop now skips a table whose columns cannot be read and continues, the same way #20224 handles the data export.

Fixes #20160.

Before submitting pull request, please review the following checklist:

  • Make sure you have read our CONTRIBUTING.md document.
  • Make sure you are making a pull request against the correct branch. For example, for bug fixes in a released version use the corresponding QA branch and for new features use the master branch. If you have a doubt, you can ask as a comment in the bug report or on the mailing list.
  • Every commit has proper Signed-off-by line as described in our DCO. This ensures that the work you're submitting is your own creation.
  • Every commit has a descriptive commit message.
  • Every commit is needed on its own, if you have just minor fixes to previous commits, you can squash them.
  • Any new functionality is covered by tests.

…re export

Signed-off-by: Eyüp Can Akman <eyupcanakman@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant