Export - CSV (All fields)
Export - CSV (Current fields)
MDEV-24282
Foreign key check should be more detailedMDEV-18126
Connect-Table-Type MYSQL: access denied when create table
Spider tables retain DESC attribute on indexes even though it has no meaning
Column CHECK referring invisible column prevents CREATE .. SELECT
TIMESTAMP incorrect attributes?
create table with serial primary key - differing result if pk declared separately
Table names have wrong case when created with LIKE
Two indexes are being created when using serial + primary key
ER_WRONG_TABLE_NAME (Incorrect table name) instead of "Incorrect path" upon CREATE TABLE with DATA/INDEX DIRECTORY
run "create table t {...} auto_increment=1000" success, but didn't take affect actually
DESC index attribute remains in Archive table definition, despite being apparently ignored
Incorrect note being written to the error log when CREATE and ALTER fail due to Row Size Too Large and in all cases for TRUNCATE and OPTIMIZE TABLE.
Period name with more than 32 symbols crashes the server
MariaDB to support Oracle like feature of External Tables
UTC_TIMESTAMP() should work with ON UPDATE for DATETIME type
Creation of table with too large definition does not obey KILL/max_statement_time
COLLATE option not accepted in generated column definition
CREATE TABLE + SELECT behaves incoherently
When you have a COMMENT and a CHECK on a column, the SHOW CREATE TABLE creates an invalid query
Case of referenced column of foreign key not corrected on import
Unfortunate error message when the same column is used for application period start and end
ASAN errors in dd_frm_type upon concurrent CREATE TABLE and TRIGGER
Incorrect information in file: './test/t0.frm' on CREATE TABLE
Temporary file is left behind upon CREATE OR REPLACE-ing on Blackhole table
FOREIGN KEY can reference any KEY, not just PRIMARY KEY and UNIQUE
Unexpected ER_TABLE_EXISTS_ERROR on primary or replica upon CREATE OR REPLACE for partitioned table
Can't create persistent generated datetime column with constant date in IF statement
create vector table failed with VECTOR INDEX when innodb_force_primary_key=on
Improve FK constraint error messages was: Foreign key constraint is incorrectly formed on 11.4.2. It works on 10.11.7
MAriadb Service crashed and galera sst sync restarted/ Forced recovery initiated
Cannot create UNIQUE index USING HASH algorithm in child columns
mariabackup fails with Error 2 on file ... open during ... table copy: No such file or directory
USAN: checking identifier names for 0 length names
CREATE TABLE ... LIKE is not documented completely
some coloums‘ length of varchar is reduced from 200 to 20,run create table sql raises exception
FKs with 'ON UPDATE CASCADE' can be set in some contexts but not others
Adding a check constraint in "create table" doesn't work if it uses a foreign key with "update cascade"
Implement CHECK constraints validation on cascading updates
Foreign key cannot be used in the check constraint
Phantom Keys
Create table w/o pkey crashed DB w/ internal error 1173
Foreign keys don't work with UNIQUE()
Creating a table using engine "SPHINX" in a Galera cluster results in an error (1235)
log_drop_table() result is not checked by callers
REFERENCES clause fails to infer multiple column names
Create table w/o pkey crashed DB w/ internal error 1173
SIGSEGV in __strcmp_evex() from my_load_defaults on INSERT when using DEFAULT_GROUP and UBSAN: runtime error: member access within null pointer of type 'struct st_my_thread_var'
create table ... as select ... results in ghost tdc if opening the table fails
CHECK constraint does not repeat in case of error
RBR skips engine for CREATE TABLE .. SELECT in ORACLE mode, further replication failure