[MDEV-11842] Fail to insert on a table where a field has no default - Jira

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Blocker
Resolution: Fixed
Affects Version/s: 10.1.21
Fix Version/s: 10.1.22, 10.2.5
Component/s: Triggers
Labels:
- 10.2-ga
- innodb
- insert
- regression
Environment:
Centos 6.8, GCL

Sprint:
10.1.22

Description

Mariadb updated this morning from 10.1.20 to 10.1.21

After the update if inserting a few fields into the table where there are other fields that have not been set and do not have defaults, The insert fails without any error. Setting default values on all fields resolves the error.

CREATE TABLE `vendors` (

	`id` INT(11) NOT NULL AUTO_INCREMENT,

	`vendor_name` VARCHAR(100) NOT NULL,

	`address1` VARCHAR(128) NOT NULL DEFAULT '',

	`address2` VARCHAR(40) NOT NULL DEFAULT '',

	`regionId` INT(11) NULL DEFAULT NULL,

	`areaId` INT(11) NULL DEFAULT NULL,

	`cityId` INT(11) NULL DEFAULT NULL,

	`townId` INT(11) NULL DEFAULT NULL,

	`city_code` VARCHAR(5) NOT NULL DEFAULT '',

	`post_code` VARCHAR(15) NOT NULL DEFAULT '',

	PRIMARY KEY (`id`)

) COLLATE='utf8_general_ci' ENGINE=InnoDB;

insert into vendors (`post_code`) VALUES ('CR0 1NN');

The above works for about 20 inserts then fails without error.

setting a default for vendor_name allows the query to work again.

Attachments

Issue Links

duplicates

MDEV-11886 Trigger prevents insert after update to 10.1.21-MariaDB-1~trusty

Closed

MDEV-11951 Triggers doesn't work

Closed

MDEV-12100 INSERT silently ignored

Closed

relates to

MDEV-19761 Before Trigger not processed for Not Null Columns if no explicit value and no DEFAULT

Closed

Activity

Ascending order - Click to sort in descending order

Habib created issue - 2017-01-19 14:50

Elena Stepanova made changes - 2017-01-23 14:48

Field	Original Value	New Value
Status	Open [ 1 ]	Confirmed [ 10101 ]

Elena Stepanova made changes - 2017-01-23 14:48

Priority

Major [ 3 ]

Blocker [ 1 ]

Elena Stepanova made changes - 2017-01-23 14:50

Description

Mariadb updated this morning from 10.1.20 to 10.1.21

After the update if inserting a few fields into the table where there are other fields that have not been set and do not have defaults, The insert fails without any error. Setting default values on all fields resolves the error.

CREATE TABLE `vendors` (
`id` INT(11) NOT NULL AUTO_INCREMENT,
`vendor_name` VARCHAR(100) NOT NULL,
`address1` VARCHAR(128) NOT NULL DEFAULT '',
`address2` VARCHAR(40) NOT NULL DEFAULT '',
`regionId` INT(11) NULL DEFAULT NULL,
`areaId` INT(11) NULL DEFAULT NULL,
`cityId` INT(11) NULL DEFAULT NULL,
`townId` INT(11) NULL DEFAULT NULL,
`city_code` VARCHAR(5) NOT NULL DEFAULT '',
`post_code` VARCHAR(15) NOT NULL DEFAULT ''
PRIMARY KEY (`id`)
COLLATE='utf8_general_ci'
ENGINE=InnoDB

insert into vendors (`post_code`) VALUES ('CR0 1NN');

The above works for about 20 inserts then fails without error.

setting a default for vendor_name allows the query to work again.

Mariadb updated this morning from 10.1.20 to 10.1.21

After the update if inserting a few fields into the table where there are other fields that have not been set and do not have defaults, The insert fails without any error. Setting default values on all fields resolves the error.

{code:sql}
CREATE TABLE `vendors` (
`id` INT(11) NOT NULL AUTO_INCREMENT,
`vendor_name` VARCHAR(100) NOT NULL,
`address1` VARCHAR(128) NOT NULL DEFAULT '',
`address2` VARCHAR(40) NOT NULL DEFAULT '',
`regionId` INT(11) NULL DEFAULT NULL,
`areaId` INT(11) NULL DEFAULT NULL,
`cityId` INT(11) NULL DEFAULT NULL,
`townId` INT(11) NULL DEFAULT NULL,
`city_code` VARCHAR(5) NOT NULL DEFAULT '',
`post_code` VARCHAR(15) NOT NULL DEFAULT '',
PRIMARY KEY (`id`)
) COLLATE='utf8_general_ci'
ENGINE=InnoDB

insert into vendors (`post_code`) VALUES ('CR0 1NN');
{code}

The above works for about 20 inserts then fails without error.

setting a default for vendor_name allows the query to work again.

Elena Stepanova made changes - 2017-01-23 14:50

Description

Mariadb updated this morning from 10.1.20 to 10.1.21

After the update if inserting a few fields into the table where there are other fields that have not been set and do not have defaults, The insert fails without any error. Setting default values on all fields resolves the error.

{code:sql}
CREATE TABLE `vendors` (
`id` INT(11) NOT NULL AUTO_INCREMENT,
`vendor_name` VARCHAR(100) NOT NULL,
`address1` VARCHAR(128) NOT NULL DEFAULT '',
`address2` VARCHAR(40) NOT NULL DEFAULT '',
`regionId` INT(11) NULL DEFAULT NULL,
`areaId` INT(11) NULL DEFAULT NULL,
`cityId` INT(11) NULL DEFAULT NULL,
`townId` INT(11) NULL DEFAULT NULL,
`city_code` VARCHAR(5) NOT NULL DEFAULT '',
`post_code` VARCHAR(15) NOT NULL DEFAULT '',
PRIMARY KEY (`id`)
) COLLATE='utf8_general_ci'
ENGINE=InnoDB

insert into vendors (`post_code`) VALUES ('CR0 1NN');
{code}

The above works for about 20 inserts then fails without error.

setting a default for vendor_name allows the query to work again.

Mariadb updated this morning from 10.1.20 to 10.1.21

After the update if inserting a few fields into the table where there are other fields that have not been set and do not have defaults, The insert fails without any error. Setting default values on all fields resolves the error.

{code:sql}
CREATE TABLE `vendors` (
`id` INT(11) NOT NULL AUTO_INCREMENT,
`vendor_name` VARCHAR(100) NOT NULL,
`address1` VARCHAR(128) NOT NULL DEFAULT '',
`address2` VARCHAR(40) NOT NULL DEFAULT '',
`regionId` INT(11) NULL DEFAULT NULL,
`areaId` INT(11) NULL DEFAULT NULL,
`cityId` INT(11) NULL DEFAULT NULL,
`townId` INT(11) NULL DEFAULT NULL,
`city_code` VARCHAR(5) NOT NULL DEFAULT '',
`post_code` VARCHAR(15) NOT NULL DEFAULT '',
PRIMARY KEY (`id`)
) COLLATE='utf8_general_ci' ENGINE=InnoDB;

insert into vendors (`post_code`) VALUES ('CR0 1NN');
{code}

The above works for about 20 inserts then fails without error.

setting a default for vendor_name allows the query to work again.

Elena Stepanova made changes - 2017-01-23 15:25

Fix Version/s		10.1 [ 16100 ]
Fix Version/s		10.2 [ 14601 ]
Assignee		Sergei Golubchik [ serg ]

Elena Stepanova made changes - 2017-01-23 15:26

Component/s

Triggers [ 10109 ]

Elena Stepanova made changes - 2017-01-23 15:26

Labels

innodb insert

innodb insert regression

Elena Stepanova made changes - 2017-01-23 16:18

Link

This issue duplicates ~~MDEV-11886~~ [ ~~MDEV-11886~~ ]

Elena Stepanova made changes - 2017-01-24 12:21

Labels

innodb insert regression

10.2-ga innodb insert regression

Elena Stepanova made changes - 2017-02-01 18:08

Link

This issue duplicates ~~MDEV-11951~~ [ ~~MDEV-11951~~ ]

Elena Stepanova made changes - 2017-02-21 10:03

Link

This issue duplicates ~~MDEV-12100~~ [ ~~MDEV-12100~~ ]

Sergei Golubchik made changes - 2017-03-01 22:59

Status

Confirmed [ 10101 ]

In Progress [ 3 ]

Sergei Golubchik made changes - 2017-03-01 22:59

Status

In Progress [ 3 ]

Stalled [ 10000 ]

Sergei Golubchik made changes - 2017-03-02 06:41

Component/s	Data Manipulation - Update [ 10805 ]
Fix Version/s		10.1.22 [ 22502 ]
Fix Version/s		10.2.5 [ 22117 ]
Fix Version/s	10.2 [ 14601 ]
Fix Version/s	10.1 [ 16100 ]
Resolution		Fixed [ 1 ]
Status	Stalled [ 10000 ]	Closed [ 6 ]

Rasmus Johansson (Inactive) made changes - 2017-03-02 12:12

Sprint

10.1.22 [ 143 ]

Anel Husakovic made changes - 2019-06-26 09:54

Link

This issue relates to ~~MDEV-19761~~ [ ~~MDEV-19761~~ ]

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

Workflow

MariaDB v3 [ 79278 ]

MariaDB v4 [ 151561 ]

People

Assignee:: Sergei Golubchik

Reporter:: Habib

Votes:: 8 Vote for this issue

Watchers:: 12 Start watching this issue

Dates

Created:: 2017-01-19 14:50

Updated:: 2019-06-26 09:54

Resolved:: 2017-03-02 06:41

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