You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please confirm if bug report does NOT exists already ?
I confirm there is no existing issue for this
Describe the problem
When the INSERT INTO statement error, but unexpected some data can be inserted successfully.
All data should not be inserted into the table.
mysql> create table t (a int);
Query OK, 0 rows affected (0.01 sec)
mysql> insert into t values (1), ('a');
ERROR 1366 (HY000): Incorrect integer value: 'a'for column 'a' at row 2
mysql>select* from t;
+------+
| a |
+------+
| 1 |
+------+
1 row inset (0.00 sec)
Expected behavior
mysql> create table t (a int);
Query OK, 0 rows affected (0.00 sec)
mysql> insert into t values (1), ('a');
ERROR 1366 (HY000): Incorrect integer value: 'a'for column 'a' at row 2
mysql>select* from t;
Empty set (0.00 sec)
How To Reproduce
droptable if exists t;
createtablet (a int);
insert into t values (1), ('a');
select*from t;
Environment
root@localhost:/# /stonedb57/install/bin/mysqld --version
/stonedb57/install/bin/mysqld Ver 5.7.36-StoneDB for Linux on x86_64 (build-)
build information as follow:
Repository address: https://github.com/stoneatom/stonedb.git:stonedb-5.7-dev
Branch name: stonedb-5.7-dev
Last commit ID: d0c2e01b6
Last commit time: Date: Wed Nov 2 19:58:00 2022 +0800
Build time: Date: Sun 06 Nov 2022 08:50:06 AM UTC
root@ub01:~# cat /etc/os-release
NAME="Ubuntu"
VERSION="20.04.5 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.5 LTS"
VERSION_ID="20.04"
Are you interested in submitting a PR to solve the problem?
Yes, I will!
The text was updated successfully, but these errors were encountered:
It is recommended to give users a warning message that transactions are not supported, so as not to mislead users into thinking that all data has not been written, but in fact some data has been inserted successfully
Have you read the Contributing Guidelines on issues?
Please confirm if bug report does NOT exists already ?
Describe the problem
When the INSERT INTO statement error, but unexpected some data can be inserted successfully.
All data should not be inserted into the table.
Expected behavior
How To Reproduce
Environment
Are you interested in submitting a PR to solve the problem?
The text was updated successfully, but these errors were encountered: