[MDEV-9124] mysqldump does not dump data if table name is same as view earlier on - Jira

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Blocker
Resolution: Fixed
Affects Version/s: 10.1.5, 10.1.8, 10.1(EOL)
Fix Version/s: 10.1.9
Component/s: Scripts & Clients
Labels:
- regression

Description

Hi everybody,

If mysqldump is run with -A (--all-databases) and a VIEW with the same name is exported as the next schema where it is a table it will not export any of the table's data.

Test script:

DROP DATABASE IF EXISTS dumped_last;

DROP DATABASE IF EXISTS dumped_first;

CREATE DATABASE dumped_last;

CREATE DATABASE dumped_first;

USE dumped_last

CREATE TABLE nonuniquename (id serial);

INSERT INTO nonuniquename VALUES(NULL);

use dumped_first

CREATE TABLE useless (id serial);

CREATE VIEW nonuniquename AS SELECT * FROM useless;

Then, dump the data:

mysqldump -A -uroot -p > dump.sql

And verify that the INSERT INTO uniquename is not present in the dump file. Please verify that 'dump_first' is dumped as first database and 'dumped_last' is dumped as second database. Also -A (or probably --all-databases) is required for this to occur.

The dump file gives a note about the 'Temporary table structure':

--

-- Temporary table structure for view `nonuniquename`

--

DROP TABLE IF EXISTS `nonuniquename`;

/*!40101 SET @saved_cs_client     = @@character_set_client */;

/*!40101 SET character_set_client = utf8 */;

CREATE TABLE `nonuniquename` (

  `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,

  UNIQUE KEY `id` (`id`)

) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=latin1;

/*!40101 SET character_set_client = @saved_cs_client */;

--

-- Current Database: `mysql`

--

Attachments

Activity

Ascending order - Click to sort in descending order

Michaël de groot created issue - 2015-11-12 19:38

Michaël de groot made changes - 2015-11-12 19:38

Field	Original Value	New Value
Description	Hi everybody, If mysqldump is run with -A (--all-databases) and a VIEW with the same name is exported as the next schema where it is a table it will not export any of the table's data. Test script: {{code}} DROP DATABASE IF EXISTS dumped_last; DROP DATABASE IF EXISTS dumped_first; CREATE DATABASE dumped_last; CREATE DATABASE dumped_first; USE dumped_last CREATE TABLE uniquename (id serial); INSERT INTO uniquename VALUES(NULL); use dumped_first CREATE TABLE useless (id serial); CREATE VIEW uniquename AS SELECT * FROM useless; {{code}} Then, dump the data: mysqldump -A -uroot -p > dump.sql And verify that the INSERT INTO uniquename is not present in the dump file. The dump file gives a note about the 'Temporary table structure': {{code}} -- -- Temporary table structure for view `uniquename` -- DROP TABLE IF EXISTS `uniquename`; /!40101 SET @saved_cs_client = @@character_set_client /; /!40101 SET character_set_client = utf8 /; CREATE TABLE `uniquename` ( `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, UNIQUE KEY `id` (`id`) ) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=latin1; /!40101 SET character_set_client = @saved_cs_client /; -- -- Current Database: `mysql` -- {{code}}	Hi everybody, If mysqldump is run with -A (--all-databases) and a VIEW with the same name is exported as the next schema where it is a table it will not export any of the table's data. Test script: {code} DROP DATABASE IF EXISTS dumped_last; DROP DATABASE IF EXISTS dumped_first; CREATE DATABASE dumped_last; CREATE DATABASE dumped_first; USE dumped_last CREATE TABLE uniquename (id serial); INSERT INTO uniquename VALUES(NULL); use dumped_first CREATE TABLE useless (id serial); CREATE VIEW uniquename AS SELECT * FROM useless; {{code}} Then, dump the data: mysqldump -A -uroot -p > dump.sql And verify that the INSERT INTO uniquename is not present in the dump file. The dump file gives a note about the 'Temporary table structure': {code} -- -- Temporary table structure for view `uniquename` -- DROP TABLE IF EXISTS `uniquename`; /!40101 SET @saved_cs_client = @@character_set_client /; /!40101 SET character_set_client = utf8 /; CREATE TABLE `uniquename` ( `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, UNIQUE KEY `id` (`id`) ) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=latin1; /!40101 SET character_set_client = @saved_cs_client /; -- -- Current Database: `mysql` -- {{code}}

Michaël de groot made changes - 2015-11-12 19:38

Description

Hi everybody,

If mysqldump is run with -A (--all-databases) and a VIEW with the same name is exported as the next schema where it is a table it will not export any of the table's data.

Test script:
{code}
DROP DATABASE IF EXISTS dumped_last;
DROP DATABASE IF EXISTS dumped_first;
CREATE DATABASE dumped_last;
CREATE DATABASE dumped_first;
USE dumped_last
CREATE TABLE uniquename (id serial);
INSERT INTO uniquename VALUES(NULL);
use dumped_first
CREATE TABLE useless (id serial);
CREATE VIEW uniquename AS SELECT * FROM useless;
{{code}}
Then, dump the data:
mysqldump -A -uroot -p > dump.sql

And verify that the INSERT INTO uniquename is not present in the dump file. The dump file gives a note about the 'Temporary table structure':
{code}
--
-- Temporary table structure for view `uniquename`
--

DROP TABLE IF EXISTS `uniquename`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;
CREATE TABLE `uniquename` (
`id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
UNIQUE KEY `id` (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=latin1;
/*!40101 SET character_set_client = @saved_cs_client */;

--
-- Current Database: `mysql`
--
{{code}}

Hi everybody,

If mysqldump is run with -A (--all-databases) and a VIEW with the same name is exported as the next schema where it is a table it will not export any of the table's data.

Test script:
{code}
DROP DATABASE IF EXISTS dumped_last;
DROP DATABASE IF EXISTS dumped_first;
CREATE DATABASE dumped_last;
CREATE DATABASE dumped_first;
USE dumped_last
CREATE TABLE uniquename (id serial);
INSERT INTO uniquename VALUES(NULL);
use dumped_first
CREATE TABLE useless (id serial);
CREATE VIEW uniquename AS SELECT * FROM useless;
{code}
Then, dump the data:
mysqldump -A -uroot -p > dump.sql

And verify that the INSERT INTO uniquename is not present in the dump file. The dump file gives a note about the 'Temporary table structure':
{code}
--
-- Temporary table structure for view `uniquename`
--

DROP TABLE IF EXISTS `uniquename`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;
CREATE TABLE `uniquename` (
`id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
UNIQUE KEY `id` (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=latin1;
/*!40101 SET character_set_client = @saved_cs_client */;

--
-- Current Database: `mysql`
--
{code}

Michaël de groot made changes - 2015-11-12 19:39

Description

Hi everybody,

If mysqldump is run with -A (--all-databases) and a VIEW with the same name is exported as the next schema where it is a table it will not export any of the table's data.

Test script:
{code}
DROP DATABASE IF EXISTS dumped_last;
DROP DATABASE IF EXISTS dumped_first;
CREATE DATABASE dumped_last;
CREATE DATABASE dumped_first;
USE dumped_last
CREATE TABLE uniquename (id serial);
INSERT INTO uniquename VALUES(NULL);
use dumped_first
CREATE TABLE useless (id serial);
CREATE VIEW uniquename AS SELECT * FROM useless;
{code}
Then, dump the data:
mysqldump -A -uroot -p > dump.sql

And verify that the INSERT INTO uniquename is not present in the dump file. The dump file gives a note about the 'Temporary table structure':
{code}
--
-- Temporary table structure for view `uniquename`
--

DROP TABLE IF EXISTS `uniquename`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;
CREATE TABLE `uniquename` (
`id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
UNIQUE KEY `id` (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=latin1;
/*!40101 SET character_set_client = @saved_cs_client */;

--
-- Current Database: `mysql`
--
{code}

Hi everybody,

If mysqldump is run with -A (--all-databases) and a VIEW with the same name is exported as the next schema where it is a table it will not export any of the table's data.

Test script:
{code}
DROP DATABASE IF EXISTS dumped_last;
DROP DATABASE IF EXISTS dumped_first;
CREATE DATABASE dumped_last;
CREATE DATABASE dumped_first;
USE dumped_last
CREATE TABLE uniquename (id serial);
INSERT INTO uniquename VALUES(NULL);
use dumped_first
CREATE TABLE useless (id serial);
CREATE VIEW uniquename AS SELECT * FROM useless;
{code}
Then, dump the data:
{code}
mysqldump -A -uroot -p > dump.sql
{code}

And verify that the INSERT INTO uniquename is not present in the dump file. Please verify that 'dump_first' is dumped as first database and 'dumped_last' is dumped as second database. Also -A (or probably --all-databases) is required for this to occur.

The dump file gives a note about the 'Temporary table structure':
{code}
--
-- Temporary table structure for view `uniquename`
--

DROP TABLE IF EXISTS `uniquename`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;
CREATE TABLE `uniquename` (
`id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
UNIQUE KEY `id` (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=latin1;
/*!40101 SET character_set_client = @saved_cs_client */;

--
-- Current Database: `mysql`
--
{code}

Michaël de groot made changes - 2015-11-12 19:44

Description

Hi everybody,

If mysqldump is run with -A (--all-databases) and a VIEW with the same name is exported as the next schema where it is a table it will not export any of the table's data.

Test script:
{code}
DROP DATABASE IF EXISTS dumped_last;
DROP DATABASE IF EXISTS dumped_first;
CREATE DATABASE dumped_last;
CREATE DATABASE dumped_first;
USE dumped_last
CREATE TABLE uniquename (id serial);
INSERT INTO uniquename VALUES(NULL);
use dumped_first
CREATE TABLE useless (id serial);
CREATE VIEW uniquename AS SELECT * FROM useless;
{code}
Then, dump the data:
{code}
mysqldump -A -uroot -p > dump.sql
{code}

And verify that the INSERT INTO uniquename is not present in the dump file. Please verify that 'dump_first' is dumped as first database and 'dumped_last' is dumped as second database. Also -A (or probably --all-databases) is required for this to occur.

The dump file gives a note about the 'Temporary table structure':
{code}
--
-- Temporary table structure for view `uniquename`
--

DROP TABLE IF EXISTS `uniquename`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;
CREATE TABLE `uniquename` (
`id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
UNIQUE KEY `id` (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=latin1;
/*!40101 SET character_set_client = @saved_cs_client */;

--
-- Current Database: `mysql`
--
{code}

Hi everybody,

If mysqldump is run with -A (--all-databases) and a VIEW with the same name is exported as the next schema where it is a table it will not export any of the table's data.

Test script:
{code}
DROP DATABASE IF EXISTS dumped_last;
DROP DATABASE IF EXISTS dumped_first;
CREATE DATABASE dumped_last;
CREATE DATABASE dumped_first;
USE dumped_last
CREATE TABLE nonuniquename (id serial);
INSERT INTO nonuniquename VALUES(NULL);
use dumped_first
CREATE TABLE useless (id serial);
CREATE VIEW nonuniquename AS SELECT * FROM useless;
{code}
Then, dump the data:
{code}
mysqldump -A -uroot -p > dump.sql
{code}

And verify that the INSERT INTO uniquename is not present in the dump file. Please verify that 'dump_first' is dumped as first database and 'dumped_last' is dumped as second database. Also -A (or probably --all-databases) is required for this to occur.

The dump file gives a note about the 'Temporary table structure':
{code}
--
-- Temporary table structure for view `uniquename`
--

DROP TABLE IF EXISTS `uniquename`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;
CREATE TABLE `uniquename` (
`id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
UNIQUE KEY `id` (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=latin1;
/*!40101 SET character_set_client = @saved_cs_client */;

--
-- Current Database: `mysql`
--
{code}

Michaël de groot made changes - 2015-11-12 19:46

Description

Hi everybody,

If mysqldump is run with -A (--all-databases) and a VIEW with the same name is exported as the next schema where it is a table it will not export any of the table's data.

Test script:
{code}
DROP DATABASE IF EXISTS dumped_last;
DROP DATABASE IF EXISTS dumped_first;
CREATE DATABASE dumped_last;
CREATE DATABASE dumped_first;
USE dumped_last
CREATE TABLE nonuniquename (id serial);
INSERT INTO nonuniquename VALUES(NULL);
use dumped_first
CREATE TABLE useless (id serial);
CREATE VIEW nonuniquename AS SELECT * FROM useless;
{code}
Then, dump the data:
{code}
mysqldump -A -uroot -p > dump.sql
{code}

And verify that the INSERT INTO uniquename is not present in the dump file. Please verify that 'dump_first' is dumped as first database and 'dumped_last' is dumped as second database. Also -A (or probably --all-databases) is required for this to occur.

The dump file gives a note about the 'Temporary table structure':
{code}
--
-- Temporary table structure for view `uniquename`
--

DROP TABLE IF EXISTS `uniquename`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;
CREATE TABLE `uniquename` (
`id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
UNIQUE KEY `id` (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=latin1;
/*!40101 SET character_set_client = @saved_cs_client */;

--
-- Current Database: `mysql`
--
{code}

Hi everybody,

If mysqldump is run with -A (--all-databases) and a VIEW with the same name is exported as the next schema where it is a table it will not export any of the table's data.

Test script:
{code}
DROP DATABASE IF EXISTS dumped_last;
DROP DATABASE IF EXISTS dumped_first;
CREATE DATABASE dumped_last;
CREATE DATABASE dumped_first;
USE dumped_last
CREATE TABLE nonuniquename (id serial);
INSERT INTO nonuniquename VALUES(NULL);
use dumped_first
CREATE TABLE useless (id serial);
CREATE VIEW nonuniquename AS SELECT * FROM useless;
{code}
Then, dump the data:
{code}
mysqldump -A -uroot -p > dump.sql
{code}

And verify that the INSERT INTO uniquename is not present in the dump file. Please verify that 'dump_first' is dumped as first database and 'dumped_last' is dumped as second database. Also -A (or probably --all-databases) is required for this to occur.

The dump file gives a note about the 'Temporary table structure':
{code}
--
-- Temporary table structure for view `nonuniquename`
--

DROP TABLE IF EXISTS `nonuniquename`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;
CREATE TABLE `nonuniquename` (
`id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
UNIQUE KEY `id` (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=latin1;
/*!40101 SET character_set_client = @saved_cs_client */;

--
-- Current Database: `mysql`
--
{code}

Elena Stepanova made changes - 2015-11-12 20:16

Status

Open [ 1 ]

Confirmed [ 10101 ]

Elena Stepanova added a comment - 2015-11-12 20:20

Thanks for the report.

The problem was introduced by the following commit:

commit ae4b24340d8f6d23ef7f4a82df3f981d65d9b060

Author: Vicențiu Ciorbaru <vicentiu@mariadb.org>

Date:   Thu Mar 19 15:16:22 2015 +0200

    MDEV-6714 mysqldump slow with tables in big databases

    mysqldump now attempts to make use of the INFORMATION_SCHEMA tables.

    If the table name is not found with a case sensitive search, it

    fallbacks to a case insensitive search.

I'm setting it to blocker because it's a regression and potential data loss.

Elena Stepanova added a comment - 2015-11-12 20:20 Thanks for the report. The problem was introduced by the following commit: commit ae4b24340d8f6d23ef7f4a82df3f981d65d9b060 Author: Vicențiu Ciorbaru <vicentiu@mariadb.org> Date: Thu Mar 19 15:16:22 2015 +0200 MDEV-6714 mysqldump slow with tables in big databases mysqldump now attempts to make use of the INFORMATION_SCHEMA tables. If the table name is not found with a case sensitive search, it fallbacks to a case insensitive search. I'm setting it to blocker because it's a regression and potential data loss.

Elena Stepanova made changes - 2015-11-12 20:20

Component/s		Scripts & Clients [ 11002 ]
Fix Version/s		10.1 [ 16100 ]
Affects Version/s		10.1.5 [ 18813 ]
Affects Version/s		10.1 [ 16100 ]
Assignee		Sergei Golubchik [ serg ]
Labels		regression
Priority	Critical [ 2 ]	Blocker [ 1 ]

Elena Stepanova made changes - 2015-11-12 20:28

Assignee

Sergei Golubchik [ serg ]

Elena Stepanova [ elenst ]

Elena Stepanova added a comment - 2015-11-12 20:44

I think this should fix it:

diff --git a/client/mysqldump.c b/client/mysqldump.c

index 05ef70a..cffa5bf 100644

--- a/client/mysqldump.c

+++ b/client/mysqldump.c

@@ -5468,7 +5468,7 @@ char check_if_ignore_table(const char *table_name, char *table_type)

   DBUG_ASSERT(2*sizeof(table_name) < sizeof(show_name_buff));

   my_snprintf(buff, sizeof(buff),

               "SELECT engine FROM INFORMATION_SCHEMA.TABLES "

-              "WHERE table_name = %s",

+              "WHERE table_schema = DATABASE() AND table_name = %s",

               quote_for_equal(table_name, show_name_buff));

   if (mysql_query_with_error_report(mysql, &res, buff))

Elena Stepanova added a comment - 2015-11-12 20:44 I think this should fix it: diff --git a/client/mysqldump.c b/client/mysqldump.c index 05ef70a..cffa5bf 100644 --- a/client/mysqldump.c +++ b/client/mysqldump.c @@ -5468,7 +5468,7 @@ char check_if_ignore_table(const char *table_name, char *table_type) DBUG_ASSERT(2*sizeof(table_name) < sizeof(show_name_buff)); my_snprintf(buff, sizeof(buff), "SELECT engine FROM INFORMATION_SCHEMA.TABLES " - "WHERE table_name = %s", + "WHERE table_schema = DATABASE() AND table_name = %s", quote_for_equal(table_name, show_name_buff)); if (mysql_query_with_error_report(mysql, &res, buff)) {

Elena Stepanova made changes - 2015-11-12 20:48

Assignee	Elena Stepanova [ elenst ]	Sergei Golubchik [ serg ]
Status	Confirmed [ 10101 ]	In Review [ 10002 ]

Vladislav Vaintroub made changes - 2015-11-12 20:50

Assignee

Sergei Golubchik [ serg ]

Vladislav Vaintroub [ wlad ]

Sergei Golubchik made changes - 2015-11-12 22:11

Description

Hi everybody,

If mysqldump is run with -A (--all-databases) and a VIEW with the same name is exported as the next schema where it is a table it will not export any of the table's data.

Test script:
{code}
DROP DATABASE IF EXISTS dumped_last;
DROP DATABASE IF EXISTS dumped_first;
CREATE DATABASE dumped_last;
CREATE DATABASE dumped_first;
USE dumped_last
CREATE TABLE nonuniquename (id serial);
INSERT INTO nonuniquename VALUES(NULL);
use dumped_first
CREATE TABLE useless (id serial);
CREATE VIEW nonuniquename AS SELECT * FROM useless;
{code}
Then, dump the data:
{code}
mysqldump -A -uroot -p > dump.sql
{code}

And verify that the INSERT INTO uniquename is not present in the dump file. Please verify that 'dump_first' is dumped as first database and 'dumped_last' is dumped as second database. Also -A (or probably --all-databases) is required for this to occur.

The dump file gives a note about the 'Temporary table structure':
{code}
--
-- Temporary table structure for view `nonuniquename`
--

DROP TABLE IF EXISTS `nonuniquename`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;
CREATE TABLE `nonuniquename` (
`id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
UNIQUE KEY `id` (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=latin1;
/*!40101 SET character_set_client = @saved_cs_client */;

--
-- Current Database: `mysql`
--
{code}

Hi everybody,

If mysqldump is run with \-A (--all-databases) and a VIEW with the same name is exported as the next schema where it is a table it will not export any of the table's data.

Test script:
{code}
DROP DATABASE IF EXISTS dumped_last;
DROP DATABASE IF EXISTS dumped_first;
CREATE DATABASE dumped_last;
CREATE DATABASE dumped_first;
USE dumped_last
CREATE TABLE nonuniquename (id serial);
INSERT INTO nonuniquename VALUES(NULL);
use dumped_first
CREATE TABLE useless (id serial);
CREATE VIEW nonuniquename AS SELECT * FROM useless;
{code}
Then, dump the data:
{code}
mysqldump -A -uroot -p > dump.sql
{code}

And verify that the INSERT INTO uniquename is not present in the dump file. Please verify that 'dump_first' is dumped as first database and 'dumped_last' is dumped as second database. Also -A (or probably --all-databases) is required for this to occur.

The dump file gives a note about the 'Temporary table structure':
{code}
--
-- Temporary table structure for view `nonuniquename`
--

DROP TABLE IF EXISTS `nonuniquename`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;
CREATE TABLE `nonuniquename` (
`id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
UNIQUE KEY `id` (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=latin1;
/*!40101 SET character_set_client = @saved_cs_client */;

--
-- Current Database: `mysql`
--
{code}

Elena Stepanova added a comment - 2015-11-13 03:35

wlad��>� elenst, https://mariadb.atlassian.net/browse/MDEV-9124 , I checked the patch it is ok. just an elaborate commit comment would we good. And , maybe an mtr test

Elena Stepanova added a comment - 2015-11-13 03:35 wlad��>� elenst, https://mariadb.atlassian.net/browse/MDEV-9124 , I checked the patch it is ok. just an elaborate commit comment would we good. And , maybe an mtr test

Elena Stepanova added a comment - 2015-11-13 03:36

https://github.com/MariaDB/server/commit/2828c2be554b62646fc990ac28b4aef20cd9b9d2

Elena Stepanova added a comment - 2015-11-13 03:36 https://github.com/MariaDB/server/commit/2828c2be554b62646fc990ac28b4aef20cd9b9d2

Elena Stepanova made changes - 2015-11-13 03:36

Fix Version/s		10.1.9 [ 20301 ]
Fix Version/s	10.1 [ 16100 ]
Assignee	Vladislav Vaintroub [ wlad ]	Elena Stepanova [ elenst ]
Resolution		Fixed [ 1 ]
Status	In Review [ 10002 ]	Closed [ 6 ]

Sergei Golubchik made changes - 2021-12-06 21:42

Workflow

MariaDB v3 [ 72531 ]

MariaDB v4 [ 149819 ]

People

Assignee:: Elena Stepanova

Reporter:: Michaël de groot

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Dates

Created:: 2015-11-12 19:38

Updated:: 2015-11-13 03:36

Resolved:: 2015-11-13 03:36

Git Integration

Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.

MariaDB Server

Details

Description

Attachments

Activity

People

Dates

Git Integration