[MDEV-9777] MyISAM and InnoDB work differently when comparing a TIME column to an empty string - Jira

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Major
Resolution: Won't Fix
Affects Version/s: 10.0(EOL)
Fix Version/s: N/A
Component/s: Optimizer
Labels:
None

Description

This bug is related to ~~MDEV-9604~~.

All problems described here were fixed in 10.1 under terms of ~~MDEV-9604~~. We now need to back-port these fixes to 10.0.

Note, the fix for 10.1 may not work for 10.0 as is, because equal field propagation in 10.1 looks very differently. So some adjusting will most likely be needed.

SET sql_mode='';

DROP TABLE IF EXISTS t1;

CREATE TABLE t1 (a ENUM('a'), b TIME, c INT, KEY(b)) ENGINE=InnoDB;

INSERT INTO t1 VALUES ('','00:00:00',0);

SELECT 1 FROM t1 WHERE (SELECT a FROM t1 group by c) = b;

ALTER TABLE t1 ENGINE=MyISAM;

SELECT 1 FROM t1 WHERE (SELECT a FROM t1 group by c) = b;

returns 0 rows for InnoDB (this is wrong)
returns 1 row for MyISAM

SET sql_mode='';

DROP TABLE IF EXISTS t1;

CREATE TABLE t1 (a ENUM('a'), b TIME, c INT, KEY(b)) ENGINE=InnoDB;

INSERT INTO t1 VALUES ('','00:00:00',0);

SELECT 1 FROM t1 WHERE (SELECT a FROM t1 group by c) = b;

ALTER TABLE t1 ENGINE=MyISAM;

SELECT 1 FROM t1 WHERE (SELECT a FROM t1 group by c) = b;

returns 0 rows for InnoDB (this is wrong)
returns 1 row for MyISAM

SET sql_mode='';

DROP TABLE IF EXISTS t1;

CREATE TABLE t1 (a ENUM('a'), b TIME, c INT, KEY(b)) ENGINE=INNODB;

INSERT INTO t1 VALUES ('','00:00:00',0);

SELECT * FROM t1 WHERE b='';

ALTER TABLE t1 ENGINE=MyISAM;

SELECT * FROM t1 WHERE b='';

returns 0 rows for InnoDB (this is wrong)
returns 1 row for MyISAM

SET sql_mode='';

DROP TABLE IF EXISTS t1;

CREATE TABLE t1 (a ENUM('a'), b TIME, c INT, KEY(b)) ENGINE=InnoDB;

INSERT INTO t1 VALUES ('','00:00:00',0);

SELECT * FROM t1 WHERE a=b;

ALTER TABLE t1 ENGINE=MyISAM;

SELECT * FROM t1 WHERE a=b;

returns 1 row for InnoDB (correctly)
returns 1 row for MyISAM (correctly)

Similar sort of inconsistency is observed with the DATE and DATETIME data types.

Attachments

Issue Links

relates to

MDEV-9604 crash in Item::save_in_field with empty enum value

Closed

Activity

Ascending order - Click to sort in descending order

Alexander Barkov created issue - 2016-03-23 04:51

Alexander Barkov made changes - 2016-03-23 04:51

Field	Original Value	New Value
Link		This issue relates to ~~MDEV-9604~~ [ ~~MDEV-9604~~ ]

Alexander Barkov made changes - 2016-03-23 04:51

Description

This bug is related to ~~MDEV-9604~~.

All problems described here were fixed in 10.1 under terms of ~~MDEV-9604~~. We now need to back-port these fixes to 10.0.

Note, the fix for 10.1 does not work for 10.0 as is, because equal field propagation in 10.1 look very differently.

{code}
DROP TABLE IF EXISTS t1;
CREATE TABLE t1 (a ENUM('a'), b TIME, c INT, KEY(b)) ENGINE=InnoDB;
INSERT INTO t1 VALUES ('','00:00:00',0);
SELECT 1 FROM t1 WHERE (SELECT a FROM t1 group by c) = b;
ALTER TABLE t1 ENGINE=MyISAM;
SELECT 1 FROM t1 WHERE (SELECT a FROM t1 group by c) = b;
{code}
- returns 0 rows for InnoDB (this is wrong)
- returns 1 row for MyISAM

{code}
DROP TABLE IF EXISTS t1;
CREATE TABLE t1 (a ENUM('a'), b TIME, c INT, KEY(b)) ENGINE=InnoDB;
INSERT INTO t1 VALUES ('','00:00:00',0);
SELECT 1 FROM t1 WHERE (SELECT a FROM t1 group by c) = b;
ALTER TABLE t1 ENGINE=MyISAM;
SELECT 1 FROM t1 WHERE (SELECT a FROM t1 group by c) = b;
{code}
- returns 0 rows for InnoDB (this is wrong)
- returns 1 row for MyISAM

{code}
DROP TABLE IF EXISTS t1;
CREATE TABLE t1 (a ENUM('a'), b TIME, c INT, KEY(b)) ENGINE=INNODB;
INSERT INTO t1 VALUES ('','00:00:00',0);
SELECT * FROM t1 WHERE b='';
ALTER TABLE t1 ENGINE=MyISAM;
SELECT * FROM t1 WHERE b='';
{code}
- returns 0 rows for InnoDB (this is wrong)
- returns 1 row for MyISAM

{code}
DROP TABLE IF EXISTS t1;
CREATE TABLE t1 (a ENUM('a'), b TIME, c INT, KEY(b)) ENGINE=InnoDB;
INSERT INTO t1 VALUES ('','00:00:00',0);
SELECT * FROM t1 WHERE a=b;
ALTER TABLE t1 ENGINE=MyISAM;
SELECT * FROM t1 WHERE a=b;
{code}
- returns 1 row for InnoDB (correctly)
- returns 1 row for MyISAM (correctly)

Similar sort of inconsistency is observed with the DATE and DATETIME data types.

This bug is related to ~~MDEV-9604~~.

All problems described here were fixed in 10.1 under terms of ~~MDEV-9604~~. We now need to back-port these fixes to 10.0.

Note, the fix for 10.1 does not work for 10.0 as is, because equal field propagation in 10.1 looks very differently.

{code}
DROP TABLE IF EXISTS t1;
CREATE TABLE t1 (a ENUM('a'), b TIME, c INT, KEY(b)) ENGINE=InnoDB;
INSERT INTO t1 VALUES ('','00:00:00',0);
SELECT 1 FROM t1 WHERE (SELECT a FROM t1 group by c) = b;
ALTER TABLE t1 ENGINE=MyISAM;
SELECT 1 FROM t1 WHERE (SELECT a FROM t1 group by c) = b;
{code}
- returns 0 rows for InnoDB (this is wrong)
- returns 1 row for MyISAM

{code}
DROP TABLE IF EXISTS t1;
CREATE TABLE t1 (a ENUM('a'), b TIME, c INT, KEY(b)) ENGINE=InnoDB;
INSERT INTO t1 VALUES ('','00:00:00',0);
SELECT 1 FROM t1 WHERE (SELECT a FROM t1 group by c) = b;
ALTER TABLE t1 ENGINE=MyISAM;
SELECT 1 FROM t1 WHERE (SELECT a FROM t1 group by c) = b;
{code}
- returns 0 rows for InnoDB (this is wrong)
- returns 1 row for MyISAM

{code}
DROP TABLE IF EXISTS t1;
CREATE TABLE t1 (a ENUM('a'), b TIME, c INT, KEY(b)) ENGINE=INNODB;
INSERT INTO t1 VALUES ('','00:00:00',0);
SELECT * FROM t1 WHERE b='';
ALTER TABLE t1 ENGINE=MyISAM;
SELECT * FROM t1 WHERE b='';
{code}
- returns 0 rows for InnoDB (this is wrong)
- returns 1 row for MyISAM

{code}
DROP TABLE IF EXISTS t1;
CREATE TABLE t1 (a ENUM('a'), b TIME, c INT, KEY(b)) ENGINE=InnoDB;
INSERT INTO t1 VALUES ('','00:00:00',0);
SELECT * FROM t1 WHERE a=b;
ALTER TABLE t1 ENGINE=MyISAM;
SELECT * FROM t1 WHERE a=b;
{code}
- returns 1 row for InnoDB (correctly)
- returns 1 row for MyISAM (correctly)

Similar sort of inconsistency is observed with the DATE and DATETIME data types.

Alexander Barkov made changes - 2016-03-23 04:52

Description

This bug is related to ~~MDEV-9604~~.

All problems described here were fixed in 10.1 under terms of ~~MDEV-9604~~. We now need to back-port these fixes to 10.0.

Note, the fix for 10.1 does not work for 10.0 as is, because equal field propagation in 10.1 looks very differently.

{code}
DROP TABLE IF EXISTS t1;
CREATE TABLE t1 (a ENUM('a'), b TIME, c INT, KEY(b)) ENGINE=InnoDB;
INSERT INTO t1 VALUES ('','00:00:00',0);
SELECT 1 FROM t1 WHERE (SELECT a FROM t1 group by c) = b;
ALTER TABLE t1 ENGINE=MyISAM;
SELECT 1 FROM t1 WHERE (SELECT a FROM t1 group by c) = b;
{code}
- returns 0 rows for InnoDB (this is wrong)
- returns 1 row for MyISAM

{code}
DROP TABLE IF EXISTS t1;
CREATE TABLE t1 (a ENUM('a'), b TIME, c INT, KEY(b)) ENGINE=InnoDB;
INSERT INTO t1 VALUES ('','00:00:00',0);
SELECT 1 FROM t1 WHERE (SELECT a FROM t1 group by c) = b;
ALTER TABLE t1 ENGINE=MyISAM;
SELECT 1 FROM t1 WHERE (SELECT a FROM t1 group by c) = b;
{code}
- returns 0 rows for InnoDB (this is wrong)
- returns 1 row for MyISAM

{code}
DROP TABLE IF EXISTS t1;
CREATE TABLE t1 (a ENUM('a'), b TIME, c INT, KEY(b)) ENGINE=INNODB;
INSERT INTO t1 VALUES ('','00:00:00',0);
SELECT * FROM t1 WHERE b='';
ALTER TABLE t1 ENGINE=MyISAM;
SELECT * FROM t1 WHERE b='';
{code}
- returns 0 rows for InnoDB (this is wrong)
- returns 1 row for MyISAM

{code}
DROP TABLE IF EXISTS t1;
CREATE TABLE t1 (a ENUM('a'), b TIME, c INT, KEY(b)) ENGINE=InnoDB;
INSERT INTO t1 VALUES ('','00:00:00',0);
SELECT * FROM t1 WHERE a=b;
ALTER TABLE t1 ENGINE=MyISAM;
SELECT * FROM t1 WHERE a=b;
{code}
- returns 1 row for InnoDB (correctly)
- returns 1 row for MyISAM (correctly)

Similar sort of inconsistency is observed with the DATE and DATETIME data types.

This bug is related to ~~MDEV-9604~~.

All problems described here were fixed in 10.1 under terms of ~~MDEV-9604~~. We now need to back-port these fixes to 10.0.

Note, the fix for 10.1 may not work for 10.0 as is, because equal field propagation in 10.1 looks very differently. So some adjusting will most likely be needed.

{code}
DROP TABLE IF EXISTS t1;
CREATE TABLE t1 (a ENUM('a'), b TIME, c INT, KEY(b)) ENGINE=InnoDB;
INSERT INTO t1 VALUES ('','00:00:00',0);
SELECT 1 FROM t1 WHERE (SELECT a FROM t1 group by c) = b;
ALTER TABLE t1 ENGINE=MyISAM;
SELECT 1 FROM t1 WHERE (SELECT a FROM t1 group by c) = b;
{code}
- returns 0 rows for InnoDB (this is wrong)
- returns 1 row for MyISAM

{code}
DROP TABLE IF EXISTS t1;
CREATE TABLE t1 (a ENUM('a'), b TIME, c INT, KEY(b)) ENGINE=InnoDB;
INSERT INTO t1 VALUES ('','00:00:00',0);
SELECT 1 FROM t1 WHERE (SELECT a FROM t1 group by c) = b;
ALTER TABLE t1 ENGINE=MyISAM;
SELECT 1 FROM t1 WHERE (SELECT a FROM t1 group by c) = b;
{code}
- returns 0 rows for InnoDB (this is wrong)
- returns 1 row for MyISAM

{code}
DROP TABLE IF EXISTS t1;
CREATE TABLE t1 (a ENUM('a'), b TIME, c INT, KEY(b)) ENGINE=INNODB;
INSERT INTO t1 VALUES ('','00:00:00',0);
SELECT * FROM t1 WHERE b='';
ALTER TABLE t1 ENGINE=MyISAM;
SELECT * FROM t1 WHERE b='';
{code}
- returns 0 rows for InnoDB (this is wrong)
- returns 1 row for MyISAM

{code}
DROP TABLE IF EXISTS t1;
CREATE TABLE t1 (a ENUM('a'), b TIME, c INT, KEY(b)) ENGINE=InnoDB;
INSERT INTO t1 VALUES ('','00:00:00',0);
SELECT * FROM t1 WHERE a=b;
ALTER TABLE t1 ENGINE=MyISAM;
SELECT * FROM t1 WHERE a=b;
{code}
- returns 1 row for InnoDB (correctly)
- returns 1 row for MyISAM (correctly)

Similar sort of inconsistency is observed with the DATE and DATETIME data types.

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

Workflow

MariaDB v3 [ 74622 ]

MariaDB v4 [ 139955 ]

Sergei Golubchik made changes - 2022-09-08 09:54

Fix Version/s

10.0 [ 16000 ]

Alexander Barkov made changes - 2022-10-26 10:16

Description

This bug is related to ~~MDEV-9604~~.

All problems described here were fixed in 10.1 under terms of ~~MDEV-9604~~. We now need to back-port these fixes to 10.0.

Note, the fix for 10.1 may not work for 10.0 as is, because equal field propagation in 10.1 looks very differently. So some adjusting will most likely be needed.

{code}
DROP TABLE IF EXISTS t1;
CREATE TABLE t1 (a ENUM('a'), b TIME, c INT, KEY(b)) ENGINE=InnoDB;
INSERT INTO t1 VALUES ('','00:00:00',0);
SELECT 1 FROM t1 WHERE (SELECT a FROM t1 group by c) = b;
ALTER TABLE t1 ENGINE=MyISAM;
SELECT 1 FROM t1 WHERE (SELECT a FROM t1 group by c) = b;
{code}
- returns 0 rows for InnoDB (this is wrong)
- returns 1 row for MyISAM

{code}
DROP TABLE IF EXISTS t1;
CREATE TABLE t1 (a ENUM('a'), b TIME, c INT, KEY(b)) ENGINE=InnoDB;
INSERT INTO t1 VALUES ('','00:00:00',0);
SELECT 1 FROM t1 WHERE (SELECT a FROM t1 group by c) = b;
ALTER TABLE t1 ENGINE=MyISAM;
SELECT 1 FROM t1 WHERE (SELECT a FROM t1 group by c) = b;
{code}
- returns 0 rows for InnoDB (this is wrong)
- returns 1 row for MyISAM

{code}
DROP TABLE IF EXISTS t1;
CREATE TABLE t1 (a ENUM('a'), b TIME, c INT, KEY(b)) ENGINE=INNODB;
INSERT INTO t1 VALUES ('','00:00:00',0);
SELECT * FROM t1 WHERE b='';
ALTER TABLE t1 ENGINE=MyISAM;
SELECT * FROM t1 WHERE b='';
{code}
- returns 0 rows for InnoDB (this is wrong)
- returns 1 row for MyISAM

{code}
DROP TABLE IF EXISTS t1;
CREATE TABLE t1 (a ENUM('a'), b TIME, c INT, KEY(b)) ENGINE=InnoDB;
INSERT INTO t1 VALUES ('','00:00:00',0);
SELECT * FROM t1 WHERE a=b;
ALTER TABLE t1 ENGINE=MyISAM;
SELECT * FROM t1 WHERE a=b;
{code}
- returns 1 row for InnoDB (correctly)
- returns 1 row for MyISAM (correctly)

Similar sort of inconsistency is observed with the DATE and DATETIME data types.

This bug is related to ~~MDEV-9604~~.

All problems described here were fixed in 10.1 under terms of ~~MDEV-9604~~. We now need to back-port these fixes to 10.0.

Note, the fix for 10.1 may not work for 10.0 as is, because equal field propagation in 10.1 looks very differently. So some adjusting will most likely be needed.

{code}
SET sql_mode='';
DROP TABLE IF EXISTS t1;
CREATE TABLE t1 (a ENUM('a'), b TIME, c INT, KEY(b)) ENGINE=InnoDB;
INSERT INTO t1 VALUES ('','00:00:00',0);
SELECT 1 FROM t1 WHERE (SELECT a FROM t1 group by c) = b;
ALTER TABLE t1 ENGINE=MyISAM;
SELECT 1 FROM t1 WHERE (SELECT a FROM t1 group by c) = b;
{code}
- returns 0 rows for InnoDB (this is wrong)
- returns 1 row for MyISAM

{code}
DROP TABLE IF EXISTS t1;
CREATE TABLE t1 (a ENUM('a'), b TIME, c INT, KEY(b)) ENGINE=InnoDB;
INSERT INTO t1 VALUES ('','00:00:00',0);
SELECT 1 FROM t1 WHERE (SELECT a FROM t1 group by c) = b;
ALTER TABLE t1 ENGINE=MyISAM;
SELECT 1 FROM t1 WHERE (SELECT a FROM t1 group by c) = b;
{code}
- returns 0 rows for InnoDB (this is wrong)
- returns 1 row for MyISAM

{code}
DROP TABLE IF EXISTS t1;
CREATE TABLE t1 (a ENUM('a'), b TIME, c INT, KEY(b)) ENGINE=INNODB;
INSERT INTO t1 VALUES ('','00:00:00',0);
SELECT * FROM t1 WHERE b='';
ALTER TABLE t1 ENGINE=MyISAM;
SELECT * FROM t1 WHERE b='';
{code}
- returns 0 rows for InnoDB (this is wrong)
- returns 1 row for MyISAM

{code}
DROP TABLE IF EXISTS t1;
CREATE TABLE t1 (a ENUM('a'), b TIME, c INT, KEY(b)) ENGINE=InnoDB;
INSERT INTO t1 VALUES ('','00:00:00',0);
SELECT * FROM t1 WHERE a=b;
ALTER TABLE t1 ENGINE=MyISAM;
SELECT * FROM t1 WHERE a=b;
{code}
- returns 1 row for InnoDB (correctly)
- returns 1 row for MyISAM (correctly)

Similar sort of inconsistency is observed with the DATE and DATETIME data types.

Alexander Barkov made changes - 2022-10-26 10:17

Description

This bug is related to ~~MDEV-9604~~.

All problems described here were fixed in 10.1 under terms of ~~MDEV-9604~~. We now need to back-port these fixes to 10.0.

Note, the fix for 10.1 may not work for 10.0 as is, because equal field propagation in 10.1 looks very differently. So some adjusting will most likely be needed.

{code}
SET sql_mode='';
DROP TABLE IF EXISTS t1;
CREATE TABLE t1 (a ENUM('a'), b TIME, c INT, KEY(b)) ENGINE=InnoDB;
INSERT INTO t1 VALUES ('','00:00:00',0);
SELECT 1 FROM t1 WHERE (SELECT a FROM t1 group by c) = b;
ALTER TABLE t1 ENGINE=MyISAM;
SELECT 1 FROM t1 WHERE (SELECT a FROM t1 group by c) = b;
{code}
- returns 0 rows for InnoDB (this is wrong)
- returns 1 row for MyISAM

{code}
DROP TABLE IF EXISTS t1;
CREATE TABLE t1 (a ENUM('a'), b TIME, c INT, KEY(b)) ENGINE=InnoDB;
INSERT INTO t1 VALUES ('','00:00:00',0);
SELECT 1 FROM t1 WHERE (SELECT a FROM t1 group by c) = b;
ALTER TABLE t1 ENGINE=MyISAM;
SELECT 1 FROM t1 WHERE (SELECT a FROM t1 group by c) = b;
{code}
- returns 0 rows for InnoDB (this is wrong)
- returns 1 row for MyISAM

{code}
DROP TABLE IF EXISTS t1;
CREATE TABLE t1 (a ENUM('a'), b TIME, c INT, KEY(b)) ENGINE=INNODB;
INSERT INTO t1 VALUES ('','00:00:00',0);
SELECT * FROM t1 WHERE b='';
ALTER TABLE t1 ENGINE=MyISAM;
SELECT * FROM t1 WHERE b='';
{code}
- returns 0 rows for InnoDB (this is wrong)
- returns 1 row for MyISAM

{code}
DROP TABLE IF EXISTS t1;
CREATE TABLE t1 (a ENUM('a'), b TIME, c INT, KEY(b)) ENGINE=InnoDB;
INSERT INTO t1 VALUES ('','00:00:00',0);
SELECT * FROM t1 WHERE a=b;
ALTER TABLE t1 ENGINE=MyISAM;
SELECT * FROM t1 WHERE a=b;
{code}
- returns 1 row for InnoDB (correctly)
- returns 1 row for MyISAM (correctly)

Similar sort of inconsistency is observed with the DATE and DATETIME data types.

This bug is related to ~~MDEV-9604~~.

All problems described here were fixed in 10.1 under terms of ~~MDEV-9604~~. We now need to back-port these fixes to 10.0.

Note, the fix for 10.1 may not work for 10.0 as is, because equal field propagation in 10.1 looks very differently. So some adjusting will most likely be needed.

{code}
SET sql_mode='';
DROP TABLE IF EXISTS t1;
CREATE TABLE t1 (a ENUM('a'), b TIME, c INT, KEY(b)) ENGINE=InnoDB;
INSERT INTO t1 VALUES ('','00:00:00',0);
SELECT 1 FROM t1 WHERE (SELECT a FROM t1 group by c) = b;
ALTER TABLE t1 ENGINE=MyISAM;
SELECT 1 FROM t1 WHERE (SELECT a FROM t1 group by c) = b;
{code}
- returns 0 rows for InnoDB (this is wrong)
- returns 1 row for MyISAM

{code}
SET sql_mode='';
DROP TABLE IF EXISTS t1;
CREATE TABLE t1 (a ENUM('a'), b TIME, c INT, KEY(b)) ENGINE=InnoDB;
INSERT INTO t1 VALUES ('','00:00:00',0);
SELECT 1 FROM t1 WHERE (SELECT a FROM t1 group by c) = b;
ALTER TABLE t1 ENGINE=MyISAM;
SELECT 1 FROM t1 WHERE (SELECT a FROM t1 group by c) = b;
{code}
- returns 0 rows for InnoDB (this is wrong)
- returns 1 row for MyISAM

{code}
SET sql_mode='';
DROP TABLE IF EXISTS t1;
CREATE TABLE t1 (a ENUM('a'), b TIME, c INT, KEY(b)) ENGINE=INNODB;
INSERT INTO t1 VALUES ('','00:00:00',0);
SELECT * FROM t1 WHERE b='';
ALTER TABLE t1 ENGINE=MyISAM;
SELECT * FROM t1 WHERE b='';
{code}
- returns 0 rows for InnoDB (this is wrong)
- returns 1 row for MyISAM

{code}
SET sql_mode='';
DROP TABLE IF EXISTS t1;
CREATE TABLE t1 (a ENUM('a'), b TIME, c INT, KEY(b)) ENGINE=InnoDB;
INSERT INTO t1 VALUES ('','00:00:00',0);
SELECT * FROM t1 WHERE a=b;
ALTER TABLE t1 ENGINE=MyISAM;
SELECT * FROM t1 WHERE a=b;
{code}
- returns 1 row for InnoDB (correctly)
- returns 1 row for MyISAM (correctly)

Similar sort of inconsistency is observed with the DATE and DATETIME data types.

Alexander Barkov added a comment - 2022-10-26 10:31

We won't backport this to 10.0, as it's out of support period.
Closing this forgotten issue.

Alexander Barkov added a comment - 2022-10-26 10:31 We won't backport this to 10.0, as it's out of support period. Closing this forgotten issue.

Alexander Barkov made changes - 2022-10-26 10:31

issue.field.resolutiondate

2022-10-26 10:31:42.0

2022-10-26 10:31:42.975

Alexander Barkov made changes - 2022-10-26 10:31

Fix Version/s		N/A [ 14700 ]
Resolution		Won't Fix [ 2 ]
Status	Open [ 1 ]	Closed [ 6 ]

People

Assignee:: Alexander Barkov

Reporter:: Alexander Barkov

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Dates

Created:: 2016-03-23 04:51

Updated:: 2022-10-26 10:31

Resolved:: 2022-10-26 10:31

Git Integration

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

MariaDB Server

Details

Description

Attachments

Issue Links

Activity

People

Dates

Git Integration