ZIP Export with discrete table files have indexes elsewhere!

[cdp1337]

PHPMyAdmin version 4.8.5
OS: CentOS (CPanel specifically)

Actions:

Select table, browse to export, expand Custom, select "Export tables as separate files". Leave all other options default.

Expected Behaviour:

Get a zip with each table self contained in its own file.

Actual Behaviour:

Got a zip (great), with each table self contained in its own file, (so far so good), WITH NO INDEXES OR AUTO INCREMENT DECLARATIONS!

For a brief example:

In %dbname%_table_blog.sql:

-- --------------------------------------------------------

--
-- Table structure for table `blog`
--

CREATE TABLE `blog` (
  `id` char(32) COLLATE utf8_unicode_ci NOT NULL,
  `site` int(15) NOT NULL DEFAULT 0 COMMENT 'The site id in multisite mode, (or -1 if global)',
  `type` enum('local','remote') COLLATE utf8_unicode_ci NOT NULL DEFAULT 'local',
  `manage_articles_permission` varchar(255) COLLATE utf8_unicode_ci NOT NULL DEFAULT '!*',
  `remote_url` varchar(255) COLLATE utf8_unicode_ci NOT NULL DEFAULT ''
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;

--
-- Dumping data for table `blog`
--

INSERT INTO `blog` (`id`, `site`, `type`, `manage_articles_permission`, `remote_url`) VALUES
('1', 0, 'local', '!*', '');

Note the lack of indexes!

Then in %dbname%_extra.sql, we have:

--
-- Indexes for table `blog`
--
ALTER TABLE `blog`
  ADD PRIMARY KEY (`id`);

... along with every other table, grouped together in a very inconvenient fashion.

---

Want to know the quickest way to slow a large application to a crawl? Import a table to replace some specific set of functionality with production data, WITHOUT THE INDEXES!

I did some hunting through the options provided in the export page, but nothing screamed Export Indexes Separately. Is there any option to not use this %dbname%_extra.sql file, but instead just keep the indexes along with the table contents where they're expected to be by any sane developer?

[cdp1337]

As an immediate follow up, if this is not native upstream functionality, but instead some CPanel / WHM trickery, I'm more than happy to yell at them instead! :)

[cdp1337]

After sleeping on this this issue, I came to the realization that historically I may not have used table-specific exports before from PMA, but instead always used mysqldump in conjunction with a custom foreach table ... script to achieve this. For this particular instance, I did not have shell access, so had to resort to the web interface to achieve a similar result. Since individual table files were provided, I simply had the blind expectation that the table file would be fully self contained with all necessary directives.

SO...... feature request!? ^_^

[williamdes]

@cdp1337 I need to investigate what you sent us, will keep you updated ^^

[williamdes]

Hi @cdp1337

Do you think this issue is still accurate with 5.0 versions ?

[williamdes]

Hi @cdp1337
I am not sure you will get this notification but just in case, could let us know if 5.1 versions fix this issue ?
Because we are missing your original table example reproducing is complicated or impossible :/