Details
-
Bug
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
10.3(EOL)
Description
This problem was originally reported by Jerome Brauge:
STRICT_TRANS_TABLES is not set in sql_mode=ORACLE.
It should be. The following script should return an error:
set sql_mode=oracle; |
create table t1 (c1 integer not null,c2 integer not null); |
insert into t1 (c1) values(1); |
Query OK, 1 row affected, 1 warning
|
Sergei also proposes to check if we should set additionally set TRADITIONAL when sql_mode=ORACLE.
Attachments
Activity
Field | Original Value | New Value |
---|---|---|
Description |
This problem was originally reported by Jerome Brauge:
STRICT_TRANS_TABLES is not set in sql_mode=ORACLE. It should be. The following script should return an error: {code:sql} set sql_mode=oracle; create table t1 (c1 integer not null,c2 integer not null); insert into t1 (c1) values(1); {code} {noformat} Query OK, 1 row affected, 1 warning {noformat} |
This problem was originally reported by Jerome Brauge:
STRICT_TRANS_TABLES is not set in sql_mode=ORACLE. It should be. The following script should return an error: {code:sql} set sql_mode=oracle; create table t1 (c1 integer not null,c2 integer not null); insert into t1 (c1) values(1); {code} {noformat} Query OK, 1 row affected, 1 warning {noformat} Sergei also proposes to check if we should set additionally set {{TRADITIONAL}} when {{sql_mode=ORACLE}}. |
Labels | Compatibility |
Fix Version/s | 10.4 [ 22408 ] | |
Fix Version/s | 10.3 [ 22126 ] |
Workflow | MariaDB v3 [ 82042 ] | MariaDB v4 [ 140383 ] |
and SIMULTANEOUS_ASSIGNMENT. But I don't think we can do it in 10.3