MDEV-10177 Invisible Columns and Invisible Index
Feature Definition:-
This feature adds invisible column functionality to server.
There is 4 level of "invisibility":
1. Not invisible (NOT_INVISIBLE) — Normal columns created by the user
2. A little bit invisible (USER_DEFINED_INVISIBLE) — columns that the
user has marked invisible. They aren't shown in SELECT * and they
don't require values in INSERT table VALUE (...). Otherwise
they behave as normal columns.
3. More invisible (SYSTEM_INVISIBLE) — Can be queried explicitly,
otherwise invisible from everything. Think ROWID sytem column.
Because they're invisible from ALTER TABLE and from CREATE TABLE
they cannot be created or dropped, they're created by the system.
User cant not create a column name which is same as of
SYSTEM_INVISIBLE.
4. Very invisible (COMPLETELY_INVISIBLE) — as above, but cannot be
queried either. They can only show up in EXPLAIN EXTENDED (might
be possible for a very invisible indexed virtual column) but
otherwise they don't exist for the user.If user creates a columns
which has same name as of COMPLETELY_INVISIBLE then
COMPLETELY_INVISIBLE column is renamed again. So it is completely
invisible from user.
Invisible Index(HA_INVISIBLE_KEY):-
Creation of invisible columns require a new type of index which
will be only visible to system. User cant see/alter/create/delete
this index. If user creates a index which is same name as of
invisible index then it will be renamed.
Syntax Details:-
Only USER_DEFINED_INVISIBLE column can be created by user. This
can be created by adding INVISIBLE suffix after column definition.
Create table t1( a int invisible, b int);
Rules:-
There are some rules/restrictions related to use of invisible columns
1. All the columns in table cant be invisible.
Create table t1(a int invisible); \\error
Create table t1(a int invisible, b int invisble); \\error
2. If you want invisible column to be NOT NULL then you have to supply
Default value for the column.
Create table t1(a int, b int not null); \\error
3. If you create a view/create table with select * then this wont copy
invisible fields. So newly created view/table wont have any invisible
columns.
Create table t2 as select * from t1;//t2 wont have t1 invisible column
Create view v1 as select * from t1;//v1 wont have t1 invisible column
4. Invisibility wont be forwarded to next table in any case of create
table/view as select */(a,b,c) from table.
Create table t2 as select a,b,c from t1; // t2 will have t1 invisible
// column(b), but this wont be invisible in t2
Create view v1 as select a,b,c from t1; // v1 will have t1 invisible
// column(b), but this wont be invisible in v1
Implementation Details:-
Parsing:- INVISIBLE_SYM is added into vcol_attribute(so its like unique
suffix), It is also added into keyword_sp_not_data_type so that table
can have column with name invisible.
Implementation detail is given by each modified function/created function.
(Some function are left as they were self explanatory)
(m= Modified, n= Newly Created)
mysql_prepare_create_table(m):- Extra checks for invisible columns are
added. Also some DEBUG_EXECUTE_IF are also added for test cases.
mysql_prepare_alter_table(m):- Now this will drop all the
COMPLETELY_INVISIBLE column and HA_INVISIBLE_KEY index. Further
Modifications are made to stop drop/change/delete of SYSTEM_INVISIBLE
column.
build_frm_image(m):- Now this allows incorporating field_visibility
status into frm image. To remain compatible with old frms
field_visibility info will be only written when any of the field is
not NOT_INVISIBLE.
extra2_write_additional_field_properties(n):- This will write field
visibility info into buffer. We first write EXTRA2_FIELD_FLAGS into
buffer/frm , then each next char will have field_visibility for each
field.
init_from_binary_frm_image(m):- Now if we get EXTRA2_FIELD_FLAGS,
then we will read the next n(n= number of fields) chars and set the
field_visibility. We also increment
thd->status_var.feature_invisible_columns. One important thing to
note if we find out that key contains a field whose visibility is
> USER_DEFINED_INVISIBLE then , we declare this key as invisible
key.
sql_show.cc is changed accordingly to make show table, show keys
correct.
mysql_insert(m):- If we get to know that we are doing insert in
this way insert into t1 values(1,1); without explicitly specifying
columns, then we check for if we have invisible fields if yes then
we reset the whole record, Why ? Because first we want hidden columns
to get default/null value. Second thing auto_increment has property
no default and no null which voilates invisible key rule 2, And
because of this it was giving error. Reseting table->record[0]
eliminates this issue. More info put breakpoint on handler::write_row
and see auto_increment value.
fill_record(m):- we continue loop if we find invisible column because
this is already reseted/will get its value if it is default.
Test cases:- Since we can not directly add > USER_DEFINED_INVISIBLE
column then I have debug_dbug to create it in mysql_prepare_create_table.
Patch Credit:- Serg Golubchik
2017-12-02 02:30:04 +01:00
|
|
|
FLUSH STATUS;
|
|
|
|
|
create table t1(abc int primary key, xyz int invisible);
|
|
|
|
|
SHOW STATUS LIKE 'Feature_invisible_columns';
|
|
|
|
|
desc t1;
|
|
|
|
|
show create table t1;
|
2017-12-07 09:28:18 +01:00
|
|
|
select TABLE_CATALOG,TABLE_SCHEMA,TABLE_NAME,COLUMN_NAME,EXTRA from INFORMATION_SCHEMA.COLUMNS where TABLE_SCHEMA='test' and TABLE_NAME='t1';
|
MDEV-10177 Invisible Columns and Invisible Index
Feature Definition:-
This feature adds invisible column functionality to server.
There is 4 level of "invisibility":
1. Not invisible (NOT_INVISIBLE) — Normal columns created by the user
2. A little bit invisible (USER_DEFINED_INVISIBLE) — columns that the
user has marked invisible. They aren't shown in SELECT * and they
don't require values in INSERT table VALUE (...). Otherwise
they behave as normal columns.
3. More invisible (SYSTEM_INVISIBLE) — Can be queried explicitly,
otherwise invisible from everything. Think ROWID sytem column.
Because they're invisible from ALTER TABLE and from CREATE TABLE
they cannot be created or dropped, they're created by the system.
User cant not create a column name which is same as of
SYSTEM_INVISIBLE.
4. Very invisible (COMPLETELY_INVISIBLE) — as above, but cannot be
queried either. They can only show up in EXPLAIN EXTENDED (might
be possible for a very invisible indexed virtual column) but
otherwise they don't exist for the user.If user creates a columns
which has same name as of COMPLETELY_INVISIBLE then
COMPLETELY_INVISIBLE column is renamed again. So it is completely
invisible from user.
Invisible Index(HA_INVISIBLE_KEY):-
Creation of invisible columns require a new type of index which
will be only visible to system. User cant see/alter/create/delete
this index. If user creates a index which is same name as of
invisible index then it will be renamed.
Syntax Details:-
Only USER_DEFINED_INVISIBLE column can be created by user. This
can be created by adding INVISIBLE suffix after column definition.
Create table t1( a int invisible, b int);
Rules:-
There are some rules/restrictions related to use of invisible columns
1. All the columns in table cant be invisible.
Create table t1(a int invisible); \\error
Create table t1(a int invisible, b int invisble); \\error
2. If you want invisible column to be NOT NULL then you have to supply
Default value for the column.
Create table t1(a int, b int not null); \\error
3. If you create a view/create table with select * then this wont copy
invisible fields. So newly created view/table wont have any invisible
columns.
Create table t2 as select * from t1;//t2 wont have t1 invisible column
Create view v1 as select * from t1;//v1 wont have t1 invisible column
4. Invisibility wont be forwarded to next table in any case of create
table/view as select */(a,b,c) from table.
Create table t2 as select a,b,c from t1; // t2 will have t1 invisible
// column(b), but this wont be invisible in t2
Create view v1 as select a,b,c from t1; // v1 will have t1 invisible
// column(b), but this wont be invisible in v1
Implementation Details:-
Parsing:- INVISIBLE_SYM is added into vcol_attribute(so its like unique
suffix), It is also added into keyword_sp_not_data_type so that table
can have column with name invisible.
Implementation detail is given by each modified function/created function.
(Some function are left as they were self explanatory)
(m= Modified, n= Newly Created)
mysql_prepare_create_table(m):- Extra checks for invisible columns are
added. Also some DEBUG_EXECUTE_IF are also added for test cases.
mysql_prepare_alter_table(m):- Now this will drop all the
COMPLETELY_INVISIBLE column and HA_INVISIBLE_KEY index. Further
Modifications are made to stop drop/change/delete of SYSTEM_INVISIBLE
column.
build_frm_image(m):- Now this allows incorporating field_visibility
status into frm image. To remain compatible with old frms
field_visibility info will be only written when any of the field is
not NOT_INVISIBLE.
extra2_write_additional_field_properties(n):- This will write field
visibility info into buffer. We first write EXTRA2_FIELD_FLAGS into
buffer/frm , then each next char will have field_visibility for each
field.
init_from_binary_frm_image(m):- Now if we get EXTRA2_FIELD_FLAGS,
then we will read the next n(n= number of fields) chars and set the
field_visibility. We also increment
thd->status_var.feature_invisible_columns. One important thing to
note if we find out that key contains a field whose visibility is
> USER_DEFINED_INVISIBLE then , we declare this key as invisible
key.
sql_show.cc is changed accordingly to make show table, show keys
correct.
mysql_insert(m):- If we get to know that we are doing insert in
this way insert into t1 values(1,1); without explicitly specifying
columns, then we check for if we have invisible fields if yes then
we reset the whole record, Why ? Because first we want hidden columns
to get default/null value. Second thing auto_increment has property
no default and no null which voilates invisible key rule 2, And
because of this it was giving error. Reseting table->record[0]
eliminates this issue. More info put breakpoint on handler::write_row
and see auto_increment value.
fill_record(m):- we continue loop if we find invisible column because
this is already reseted/will get its value if it is default.
Test cases:- Since we can not directly add > USER_DEFINED_INVISIBLE
column then I have debug_dbug to create it in mysql_prepare_create_table.
Patch Credit:- Serg Golubchik
2017-12-02 02:30:04 +01:00
|
|
|
drop table t1;
|
|
|
|
|
--error ER_TABLE_MUST_HAVE_COLUMNS
|
|
|
|
|
create table t1(a1 int invisible);
|
|
|
|
|
--error ER_PARSE_ERROR
|
|
|
|
|
create table t1(a1 blob,invisible(a1));
|
|
|
|
|
--error ER_INVISIBLE_NOT_NULL_WITHOUT_DEFAULT
|
|
|
|
|
create table t1(a1 int primary key invisible ,a2 int unique invisible , a3 blob,a4 int not null invisible unique);
|
2018-01-29 08:01:07 +01:00
|
|
|
--error ER_TABLE_MUST_HAVE_COLUMNS
|
MDEV-10177 Invisible Columns and Invisible Index
Feature Definition:-
This feature adds invisible column functionality to server.
There is 4 level of "invisibility":
1. Not invisible (NOT_INVISIBLE) — Normal columns created by the user
2. A little bit invisible (USER_DEFINED_INVISIBLE) — columns that the
user has marked invisible. They aren't shown in SELECT * and they
don't require values in INSERT table VALUE (...). Otherwise
they behave as normal columns.
3. More invisible (SYSTEM_INVISIBLE) — Can be queried explicitly,
otherwise invisible from everything. Think ROWID sytem column.
Because they're invisible from ALTER TABLE and from CREATE TABLE
they cannot be created or dropped, they're created by the system.
User cant not create a column name which is same as of
SYSTEM_INVISIBLE.
4. Very invisible (COMPLETELY_INVISIBLE) — as above, but cannot be
queried either. They can only show up in EXPLAIN EXTENDED (might
be possible for a very invisible indexed virtual column) but
otherwise they don't exist for the user.If user creates a columns
which has same name as of COMPLETELY_INVISIBLE then
COMPLETELY_INVISIBLE column is renamed again. So it is completely
invisible from user.
Invisible Index(HA_INVISIBLE_KEY):-
Creation of invisible columns require a new type of index which
will be only visible to system. User cant see/alter/create/delete
this index. If user creates a index which is same name as of
invisible index then it will be renamed.
Syntax Details:-
Only USER_DEFINED_INVISIBLE column can be created by user. This
can be created by adding INVISIBLE suffix after column definition.
Create table t1( a int invisible, b int);
Rules:-
There are some rules/restrictions related to use of invisible columns
1. All the columns in table cant be invisible.
Create table t1(a int invisible); \\error
Create table t1(a int invisible, b int invisble); \\error
2. If you want invisible column to be NOT NULL then you have to supply
Default value for the column.
Create table t1(a int, b int not null); \\error
3. If you create a view/create table with select * then this wont copy
invisible fields. So newly created view/table wont have any invisible
columns.
Create table t2 as select * from t1;//t2 wont have t1 invisible column
Create view v1 as select * from t1;//v1 wont have t1 invisible column
4. Invisibility wont be forwarded to next table in any case of create
table/view as select */(a,b,c) from table.
Create table t2 as select a,b,c from t1; // t2 will have t1 invisible
// column(b), but this wont be invisible in t2
Create view v1 as select a,b,c from t1; // v1 will have t1 invisible
// column(b), but this wont be invisible in v1
Implementation Details:-
Parsing:- INVISIBLE_SYM is added into vcol_attribute(so its like unique
suffix), It is also added into keyword_sp_not_data_type so that table
can have column with name invisible.
Implementation detail is given by each modified function/created function.
(Some function are left as they were self explanatory)
(m= Modified, n= Newly Created)
mysql_prepare_create_table(m):- Extra checks for invisible columns are
added. Also some DEBUG_EXECUTE_IF are also added for test cases.
mysql_prepare_alter_table(m):- Now this will drop all the
COMPLETELY_INVISIBLE column and HA_INVISIBLE_KEY index. Further
Modifications are made to stop drop/change/delete of SYSTEM_INVISIBLE
column.
build_frm_image(m):- Now this allows incorporating field_visibility
status into frm image. To remain compatible with old frms
field_visibility info will be only written when any of the field is
not NOT_INVISIBLE.
extra2_write_additional_field_properties(n):- This will write field
visibility info into buffer. We first write EXTRA2_FIELD_FLAGS into
buffer/frm , then each next char will have field_visibility for each
field.
init_from_binary_frm_image(m):- Now if we get EXTRA2_FIELD_FLAGS,
then we will read the next n(n= number of fields) chars and set the
field_visibility. We also increment
thd->status_var.feature_invisible_columns. One important thing to
note if we find out that key contains a field whose visibility is
> USER_DEFINED_INVISIBLE then , we declare this key as invisible
key.
sql_show.cc is changed accordingly to make show table, show keys
correct.
mysql_insert(m):- If we get to know that we are doing insert in
this way insert into t1 values(1,1); without explicitly specifying
columns, then we check for if we have invisible fields if yes then
we reset the whole record, Why ? Because first we want hidden columns
to get default/null value. Second thing auto_increment has property
no default and no null which voilates invisible key rule 2, And
because of this it was giving error. Reseting table->record[0]
eliminates this issue. More info put breakpoint on handler::write_row
and see auto_increment value.
fill_record(m):- we continue loop if we find invisible column because
this is already reseted/will get its value if it is default.
Test cases:- Since we can not directly add > USER_DEFINED_INVISIBLE
column then I have debug_dbug to create it in mysql_prepare_create_table.
Patch Credit:- Serg Golubchik
2017-12-02 02:30:04 +01:00
|
|
|
create table t1(abc int not null invisible);
|
2018-01-29 08:01:07 +01:00
|
|
|
--echo MDEV-14849 CREATE + ALTER with user-invisible columns produce invalid table definition
|
|
|
|
|
create or replace table t1 (pk int auto_increment primary key invisible, i int);
|
|
|
|
|
--error ER_INVISIBLE_NOT_NULL_WITHOUT_DEFAULT
|
|
|
|
|
alter table t1 modify pk int invisible;
|
|
|
|
|
drop table t1;
|
MDEV-10177 Invisible Columns and Invisible Index
Feature Definition:-
This feature adds invisible column functionality to server.
There is 4 level of "invisibility":
1. Not invisible (NOT_INVISIBLE) — Normal columns created by the user
2. A little bit invisible (USER_DEFINED_INVISIBLE) — columns that the
user has marked invisible. They aren't shown in SELECT * and they
don't require values in INSERT table VALUE (...). Otherwise
they behave as normal columns.
3. More invisible (SYSTEM_INVISIBLE) — Can be queried explicitly,
otherwise invisible from everything. Think ROWID sytem column.
Because they're invisible from ALTER TABLE and from CREATE TABLE
they cannot be created or dropped, they're created by the system.
User cant not create a column name which is same as of
SYSTEM_INVISIBLE.
4. Very invisible (COMPLETELY_INVISIBLE) — as above, but cannot be
queried either. They can only show up in EXPLAIN EXTENDED (might
be possible for a very invisible indexed virtual column) but
otherwise they don't exist for the user.If user creates a columns
which has same name as of COMPLETELY_INVISIBLE then
COMPLETELY_INVISIBLE column is renamed again. So it is completely
invisible from user.
Invisible Index(HA_INVISIBLE_KEY):-
Creation of invisible columns require a new type of index which
will be only visible to system. User cant see/alter/create/delete
this index. If user creates a index which is same name as of
invisible index then it will be renamed.
Syntax Details:-
Only USER_DEFINED_INVISIBLE column can be created by user. This
can be created by adding INVISIBLE suffix after column definition.
Create table t1( a int invisible, b int);
Rules:-
There are some rules/restrictions related to use of invisible columns
1. All the columns in table cant be invisible.
Create table t1(a int invisible); \\error
Create table t1(a int invisible, b int invisble); \\error
2. If you want invisible column to be NOT NULL then you have to supply
Default value for the column.
Create table t1(a int, b int not null); \\error
3. If you create a view/create table with select * then this wont copy
invisible fields. So newly created view/table wont have any invisible
columns.
Create table t2 as select * from t1;//t2 wont have t1 invisible column
Create view v1 as select * from t1;//v1 wont have t1 invisible column
4. Invisibility wont be forwarded to next table in any case of create
table/view as select */(a,b,c) from table.
Create table t2 as select a,b,c from t1; // t2 will have t1 invisible
// column(b), but this wont be invisible in t2
Create view v1 as select a,b,c from t1; // v1 will have t1 invisible
// column(b), but this wont be invisible in v1
Implementation Details:-
Parsing:- INVISIBLE_SYM is added into vcol_attribute(so its like unique
suffix), It is also added into keyword_sp_not_data_type so that table
can have column with name invisible.
Implementation detail is given by each modified function/created function.
(Some function are left as they were self explanatory)
(m= Modified, n= Newly Created)
mysql_prepare_create_table(m):- Extra checks for invisible columns are
added. Also some DEBUG_EXECUTE_IF are also added for test cases.
mysql_prepare_alter_table(m):- Now this will drop all the
COMPLETELY_INVISIBLE column and HA_INVISIBLE_KEY index. Further
Modifications are made to stop drop/change/delete of SYSTEM_INVISIBLE
column.
build_frm_image(m):- Now this allows incorporating field_visibility
status into frm image. To remain compatible with old frms
field_visibility info will be only written when any of the field is
not NOT_INVISIBLE.
extra2_write_additional_field_properties(n):- This will write field
visibility info into buffer. We first write EXTRA2_FIELD_FLAGS into
buffer/frm , then each next char will have field_visibility for each
field.
init_from_binary_frm_image(m):- Now if we get EXTRA2_FIELD_FLAGS,
then we will read the next n(n= number of fields) chars and set the
field_visibility. We also increment
thd->status_var.feature_invisible_columns. One important thing to
note if we find out that key contains a field whose visibility is
> USER_DEFINED_INVISIBLE then , we declare this key as invisible
key.
sql_show.cc is changed accordingly to make show table, show keys
correct.
mysql_insert(m):- If we get to know that we are doing insert in
this way insert into t1 values(1,1); without explicitly specifying
columns, then we check for if we have invisible fields if yes then
we reset the whole record, Why ? Because first we want hidden columns
to get default/null value. Second thing auto_increment has property
no default and no null which voilates invisible key rule 2, And
because of this it was giving error. Reseting table->record[0]
eliminates this issue. More info put breakpoint on handler::write_row
and see auto_increment value.
fill_record(m):- we continue loop if we find invisible column because
this is already reseted/will get its value if it is default.
Test cases:- Since we can not directly add > USER_DEFINED_INVISIBLE
column then I have debug_dbug to create it in mysql_prepare_create_table.
Patch Credit:- Serg Golubchik
2017-12-02 02:30:04 +01:00
|
|
|
create table t1(a int invisible, b int);
|
|
|
|
|
#should automatically add null
|
|
|
|
|
insert into t1 values(1);
|
|
|
|
|
insert into t1(a) values(2);
|
|
|
|
|
insert into t1(b) values(3);
|
|
|
|
|
insert into t1(a,b) values(5,5);
|
|
|
|
|
select * from t1;
|
|
|
|
|
select a,b from t1;
|
|
|
|
|
delete from t1;
|
|
|
|
|
insert into t1 values(1),(2),(3),(4);
|
|
|
|
|
select * from t1;
|
|
|
|
|
select a from t1;
|
|
|
|
|
drop table t1;
|
|
|
|
|
|
|
|
|
|
--echo #more complex case of invisible
|
|
|
|
|
create table t1(a int , b int invisible , c int invisible auto_increment unique, d blob , e int unique, f int);
|
|
|
|
|
desc t1;
|
|
|
|
|
insert into t1 values(1,'d blob',1,1),(1,'d blob',11,1),(1,'d blob',2,1),(1,'d blob',3,1),(1,'d blob',41,1);
|
|
|
|
|
select * from t1;
|
|
|
|
|
select a,b,c,d,e,f from t1;
|
|
|
|
|
drop table t1;
|
|
|
|
|
|
|
|
|
|
--echo #more complex case of invisible with sql_mode=NO_AUTO_VALUE_ON_ZERO
|
|
|
|
|
set sql_mode='NO_AUTO_VALUE_ON_ZERO';
|
|
|
|
|
create table t1(a int , b int invisible , c int invisible auto_increment unique, d blob , e int unique, f int);
|
|
|
|
|
desc t1;
|
|
|
|
|
insert into t1 values(1,'d blob',1,1),(1,'d blob',11,1),(1,'d blob',2,1),(1,'d blob',3,1),(1,'d blob',41,1);
|
|
|
|
|
select * from t1;
|
|
|
|
|
select a,b,c,d,e,f from t1;
|
|
|
|
|
drop table t1;
|
|
|
|
|
set sql_mode='';
|
|
|
|
|
|
|
|
|
|
--error ER_PARSE_ERROR
|
|
|
|
|
create table sdsdsd(a int , b int, invisible(a,b));
|
|
|
|
|
create table t1(a int,abc int as (a mod 3) virtual invisible);
|
|
|
|
|
desc t1;
|
|
|
|
|
--error ER_WRONG_VALUE_COUNT_ON_ROW
|
|
|
|
|
insert into t1 values(1,default);
|
|
|
|
|
insert into t1 values(1),(22),(233);
|
|
|
|
|
select * from t1;
|
|
|
|
|
select a,abc from t1;
|
|
|
|
|
drop table t1;
|
|
|
|
|
create table t1(abc int primary key invisible auto_increment, a int);
|
|
|
|
|
desc t1;
|
|
|
|
|
show create table t1;
|
|
|
|
|
insert into t1 values(1);
|
|
|
|
|
insert into t1 values(2);
|
|
|
|
|
insert into t1 values(3);
|
|
|
|
|
select * from t1;
|
|
|
|
|
select abc,a from t1;
|
|
|
|
|
delete from t1;
|
|
|
|
|
insert into t1 values(1),(2),(3),(4),(6);
|
|
|
|
|
select abc,a from t1;
|
|
|
|
|
drop table t1;
|
|
|
|
|
create table t1(abc int);
|
|
|
|
|
--error ER_TABLE_MUST_HAVE_COLUMNS
|
|
|
|
|
alter table t1 change abc ss int invisible;
|
|
|
|
|
alter table t1 add column xyz int;
|
|
|
|
|
alter table t1 modify column abc int ;
|
|
|
|
|
desc t1;
|
|
|
|
|
--error ER_WRONG_VALUE_COUNT_ON_ROW
|
|
|
|
|
insert into t1 values(22);
|
|
|
|
|
alter table t1 modify column abc int invisible;
|
|
|
|
|
desc t1;
|
|
|
|
|
insert into t1 values(12);
|
|
|
|
|
drop table t1;
|
|
|
|
|
--echo #some test on copy table structure with table data;
|
|
|
|
|
--echo #table with invisible fields and unique keys;
|
|
|
|
|
create table t1(a int , b int invisible , c int invisible auto_increment unique, d blob , e int unique, f int);
|
|
|
|
|
desc t1;
|
|
|
|
|
insert into t1 values(1,'d blob',1,1),(1,'d blob',11,1),(1,'d blob',2,1),(1,'d blob',3,1),(1,'d blob',41,1);
|
|
|
|
|
select * from t1;
|
|
|
|
|
select a,b,c,d,e,f from t1;
|
|
|
|
|
--echo #this won't copy invisible fields and keys;
|
|
|
|
|
create table t2 as select * from t1;
|
|
|
|
|
desc t2;
|
|
|
|
|
select * from t2;
|
|
|
|
|
--error ER_BAD_FIELD_ERROR
|
|
|
|
|
select a,b,c,d,e,f from t2;
|
|
|
|
|
drop table t2;
|
|
|
|
|
--echo #now this will copy invisible fields
|
|
|
|
|
create table t2 as select a,b,c,d,e,f from t1;
|
|
|
|
|
desc t2;
|
|
|
|
|
select * from t2;
|
|
|
|
|
select a,b,c,d,e,f from t2;
|
|
|
|
|
drop table t2,t1;
|
|
|
|
|
--echo #some test related to copy of data from one table to another;
|
|
|
|
|
create table t1(a int , b int invisible , c int invisible auto_increment unique, d blob , e int unique, f int);
|
|
|
|
|
insert into t1 values(1,'d blob',1,1),(1,'d blob',11,1),(1,'d blob',2,1),(1,'d blob',3,1),(1,'d blob',41,1);
|
|
|
|
|
select a,b,c,d,e,f from t1;
|
|
|
|
|
create table t2(a int , b int invisible , c int invisible , d blob , e int unique, f int);
|
|
|
|
|
insert into t2 select * from t1;
|
|
|
|
|
select a,b,c,d,e,f from t2;
|
|
|
|
|
truncate t2;
|
|
|
|
|
insert into t2 (a,b,c,d,e,f) select a,b,c,d,e,f from t1;
|
|
|
|
|
select a,b,c,d,e,f from t2;
|
|
|
|
|
truncate t2;
|
|
|
|
|
drop table t1,t2;
|
|
|
|
|
--echo #some test related to creating view on table with invisible column;
|
|
|
|
|
create table t1(a int , b int invisible , c int invisible auto_increment unique, d blob , e int unique, f int);
|
|
|
|
|
insert into t1 values(1,'d blob',1,1),(1,'d blob',11,1),(1,'d blob',2,1),(1,'d blob',3,1),(1,'d blob',41,1);
|
|
|
|
|
create view v as select * from t1;
|
|
|
|
|
desc v;
|
|
|
|
|
select * from v;
|
|
|
|
|
--echo #v does not have invisible column;
|
|
|
|
|
--error ER_BAD_FIELD_ERROR
|
|
|
|
|
select a,b,c,d,e,f from v;
|
|
|
|
|
insert into v values(1,21,32,4);
|
|
|
|
|
select * from v;
|
|
|
|
|
--error ER_BAD_FIELD_ERROR
|
|
|
|
|
insert into v(a,b,c,d,e,f) values(1,12,3,4,5,6);
|
|
|
|
|
drop view v;
|
|
|
|
|
create view v as select a,b,c,d,e,f from t1;
|
|
|
|
|
desc v;
|
|
|
|
|
select * from v;
|
|
|
|
|
--echo #v does have invisible column but they aren't invisible anymore.
|
|
|
|
|
select a,b,c,d,e,f from v;
|
|
|
|
|
insert into v values(1,26,33,4,45,66);
|
|
|
|
|
select a,b,c,d,e,f from v;
|
|
|
|
|
insert into v(a,b,c,d,e,f) values(1,32,31,41,5,6);
|
|
|
|
|
select a,b,c,d,e,f from v;
|
|
|
|
|
drop view v;
|
|
|
|
|
drop table t1;
|
|
|
|
|
--echo #now invisible column in where and some join query
|
|
|
|
|
create table t1 (a int unique , b int invisible unique, c int unique invisible);
|
|
|
|
|
insert into t1(a,b,c) values(1,1,1);
|
|
|
|
|
insert into t1(a,b,c) values(2,2,2);
|
|
|
|
|
insert into t1(a,b,c) values(3,3,3);
|
|
|
|
|
insert into t1(a,b,c) values(4,4,4);
|
|
|
|
|
insert into t1(a,b,c) values(21,21,26);
|
|
|
|
|
insert into t1(a,b,c) values(31,31,35);
|
|
|
|
|
insert into t1(a,b,c) values(41,41,45);
|
|
|
|
|
insert into t1(a,b,c) values(22,22,24);
|
|
|
|
|
insert into t1(a,b,c) values(32,32,33);
|
|
|
|
|
insert into t1(a,b,c) values(42,42,43);
|
|
|
|
|
explain select * from t1 where b=3;
|
|
|
|
|
select * from t1 where b=3;
|
|
|
|
|
explain select * from t1 where c=3;
|
|
|
|
|
select * from t1 where c=3;
|
|
|
|
|
create table t2 as select a,b,c from t1;
|
|
|
|
|
desc t2;
|
|
|
|
|
explain select * from t1,t2 where t1.b = t2.c and t1.c = t2.b;
|
|
|
|
|
select * from t1,t2 where t1.b = t2.c and t1.c = t2.b;
|
|
|
|
|
drop table t1,t2;
|
|
|
|
|
--echo #Unhide invisible columns
|
|
|
|
|
create table t1 (a int primary key, b int invisible, c int invisible unique);
|
|
|
|
|
show create table t1;
|
|
|
|
|
desc t1;
|
|
|
|
|
alter table t1 modify column b int;
|
|
|
|
|
desc t1;
|
|
|
|
|
alter table t1 change column c d int;
|
|
|
|
|
desc t1;
|
|
|
|
|
drop table t1;
|
|
|
|
|
SHOW STATUS LIKE 'Feature_invisible_columns';
|
|
|
|
|
--echo #invisible is non reserved
|
|
|
|
|
create table t1(a int unique , invisible int invisible, c int );
|
|
|
|
|
desc t1;
|
|
|
|
|
alter table t1 change column invisible hid int invisible;
|
|
|
|
|
desc t1;
|
|
|
|
|
drop table t1;
|
|
|
|
|
##Internal temp table
|
|
|
|
|
CREATE TABLE t1 (b int);
|
|
|
|
|
INSERT t1 values(1);
|
|
|
|
|
INSERT t1 values(2);
|
|
|
|
|
INSERT t1 values(3);
|
|
|
|
|
INSERT t1 values(4);
|
|
|
|
|
INSERT t1 values(5);
|
|
|
|
|
CREATE TABLE t2 (a int invisible) SELECT * FROM t1;
|
|
|
|
|
select * from t2 order by b;
|
|
|
|
|
select a,b from t2 order by b;
|
|
|
|
|
CREATE TABLE t3 (b int, a int invisible) SELECT * FROM t1;
|
|
|
|
|
select * from t3 order by b;
|
|
|
|
|
select a,b from t3 order by b;
|
|
|
|
|
--error ER_TABLE_MUST_HAVE_COLUMNS
|
|
|
|
|
CREATE TABLE t4 (b int invisible) SELECT * FROM t1;
|
|
|
|
|
--error ER_TABLE_MUST_HAVE_COLUMNS
|
|
|
|
|
CREATE TABLE t5 (a int invisible) SELECT b as a FROM t1;
|
|
|
|
|
drop table t1,t2,t3;
|
|
|
|
|
|
|
|
|
|
create table t1 (a int , b int invisible default 3, c int , d int invisible default 6);
|
|
|
|
|
DELIMITER //;
|
|
|
|
|
CREATE PROCEDURE
|
|
|
|
|
insert_t1(a int, b int)
|
|
|
|
|
MODIFIES SQL DATA
|
|
|
|
|
insert into t1 values(a,b);
|
|
|
|
|
//
|
|
|
|
|
DELIMITER ;//
|
|
|
|
|
call insert_t1(1,1);
|
|
|
|
|
call insert_t1(2,2);
|
|
|
|
|
select * from t1 order by a;
|
|
|
|
|
select a,b,c,d from t1 order by a;
|
|
|
|
|
DROP PROCEDURE insert_t1;
|
|
|
|
|
delete from t1;
|
|
|
|
|
prepare insert_1 from "insert into t1 values(@a,@c)";
|
|
|
|
|
prepare insert_2 from "insert into t1(a,b,c) values(@a,@b,@c)";
|
|
|
|
|
set @a=1, @c=1;
|
|
|
|
|
execute insert_1;
|
|
|
|
|
set @a=2,@b=2, @c=2;
|
|
|
|
|
execute insert_2;
|
|
|
|
|
select a,b,c,d from t1 order by a;
|
2018-01-30 09:34:05 +01:00
|
|
|
drop table t1;
|
|
|
|
|
#MDEV-15085 Non constant default getting Null values
|
|
|
|
|
create table t1(a int default 5 invisible, b int);
|
|
|
|
|
create table t2(a int default (b+11) invisible, b int);
|
|
|
|
|
insert into t1 values(1);
|
|
|
|
|
select a,b from t1;
|
|
|
|
|
insert into t2 values(1);
|
|
|
|
|
select a,b from t2;
|
2018-02-08 17:34:30 +01:00
|
|
|
drop table t1,t2;
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# natural join and using
|
|
|
|
|
#
|
|
|
|
|
create table t1 (a int invisible, b int, c int);
|
|
|
|
|
create table t2 (a int, b int, d int);
|
|
|
|
|
insert t1 (a,b,c) values (0,2,3), (10, 20, 30);
|
|
|
|
|
insert t2 (a,b,d) values (1,2,4), (10, 30, 40);
|
|
|
|
|
select * from t1 join t2 using (a);
|
|
|
|
|
select * from t1 natural join t2;
|
|
|
|
|
drop table t1, t2;
|
2018-04-16 12:57:11 +02:00
|
|
|
## Triggers MDEV-15754
|
|
|
|
|
CREATE TABLE t1 (c CHAR(3), t TIMESTAMP invisible);
|
|
|
|
|
INSERT INTO t1 (c,t) VALUES ('foo','2000-01-01 00:00:00');
|
|
|
|
|
|
|
|
|
|
CREATE TRIGGER tr BEFORE INSERT ON t1 FOR EACH ROW SET @a= 1;
|
|
|
|
|
INSERT INTO t1 SELECT * FROM t1;
|
|
|
|
|
# Cleanup
|
|
|
|
|
DROP TABLE t1;
|
2018-04-26 13:19:27 +02:00
|
|
|
##LOAD DATA MDEV-15965 Invisible columns and LOAD DATA don't work well
|
|
|
|
|
## together: ER_WARN_TOO_FEW_RECORDS
|
|
|
|
|
create or replace table t1 (a int, b int invisible);
|
|
|
|
|
insert into t1 values (1),(2);
|
|
|
|
|
|
2023-05-31 06:57:45 +02:00
|
|
|
--disable_ps2_protocol
|
2018-04-26 13:19:27 +02:00
|
|
|
select * from t1 into outfile 'f';
|
2023-05-31 06:57:45 +02:00
|
|
|
--enable_ps2_protocol
|
2018-04-26 13:19:27 +02:00
|
|
|
load data infile 'f' into table t1;
|
|
|
|
|
select a,b from t1;
|
|
|
|
|
load data infile 'f' into table t1 (a,@v) SET b=@v;
|
|
|
|
|
select a,b from t1;
|
|
|
|
|
load data infile 'f' into table t1 (a,@v) SET b=a;
|
|
|
|
|
select a,b from t1;
|
|
|
|
|
truncate table t1;
|
|
|
|
|
|
|
|
|
|
insert into t1(a,b) values (1,1),(2,2);
|
2023-05-31 06:57:45 +02:00
|
|
|
--disable_ps2_protocol
|
2018-04-26 13:19:27 +02:00
|
|
|
select a,b from t1 into outfile 'a';
|
2023-05-31 06:57:45 +02:00
|
|
|
--enable_ps2_protocol
|
2018-04-26 13:19:27 +02:00
|
|
|
load data infile 'a' into table t1(a,b);
|
|
|
|
|
select a,b from t1;
|
|
|
|
|
load data infile 'a' into table t1 (a,@v) SET b=@v;
|
|
|
|
|
select a,b from t1;
|
|
|
|
|
load data infile 'a' into table t1 (a,@v) SET b=@v+2;
|
|
|
|
|
select a,b from t1;
|
|
|
|
|
|
|
|
|
|
#cleanup
|
|
|
|
|
drop table t1;
|
2020-08-25 21:21:07 +02:00
|
|
|
|
|
|
|
|
--echo #
|
|
|
|
|
--echo # MDEV-23467 SIGSEGV in fill_record/fill_record_n_invoke_before_triggers on INSERT DELAYED
|
|
|
|
|
--echo #
|
|
|
|
|
create table t1 (a int, b int invisible);
|
|
|
|
|
insert delayed into t1 values (1);
|
|
|
|
|
# cleanup
|
|
|
|
|
drop table t1;
|
2021-10-11 12:36:07 +02:00
|
|
|
|
|
|
|
|
--echo #
|
|
|
|
|
--echo # MDEV-25891 Computed default for INVISIBLE column is ignored in INSERT
|
|
|
|
|
--echo #
|
|
|
|
|
create table t1(
|
|
|
|
|
a int,
|
|
|
|
|
x int default (a),
|
|
|
|
|
y int default (a) invisible,
|
|
|
|
|
z int default (33) invisible);
|
|
|
|
|
insert into t1 values (1, default);
|
|
|
|
|
insert into t1 (a) values (2);
|
|
|
|
|
select a, x, y, z from t1;
|
|
|
|
|
drop table t1;
|