2012-09-09 00:22:06 +02:00
|
|
|
drop table if exists t1;
|
2015-08-11 18:45:38 +02:00
|
|
|
set sql_mode="";
|
2014-07-19 16:46:08 +02:00
|
|
|
flush status;
|
2012-09-09 00:22:06 +02:00
|
|
|
show status like "feature%";
|
|
|
|
|
Variable_name Value
|
2019-03-22 12:08:34 +01:00
|
|
|
Feature_application_time_periods 0
|
2016-07-25 22:15:05 +02:00
|
|
|
Feature_check_constraint 0
|
2018-03-30 00:25:48 +02:00
|
|
|
Feature_custom_aggregate_functions 0
|
2014-07-19 16:46:08 +02:00
|
|
|
Feature_delay_key_write 0
|
2012-09-09 00:22:06 +02:00
|
|
|
Feature_dynamic_columns 0
|
|
|
|
|
Feature_fulltext 0
|
|
|
|
|
Feature_gis 0
|
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
|
|
|
Feature_invisible_columns 0
|
2018-04-26 21:12:51 +02:00
|
|
|
Feature_json 0
|
2012-09-09 00:22:06 +02:00
|
|
|
Feature_locale 0
|
|
|
|
|
Feature_subquery 0
|
2018-04-28 19:40:34 +02:00
|
|
|
Feature_system_versioning 0
|
2012-09-09 00:22:06 +02:00
|
|
|
Feature_timezone 0
|
|
|
|
|
Feature_trigger 0
|
2016-09-20 22:20:25 +02:00
|
|
|
Feature_window_functions 0
|
2012-09-09 00:22:06 +02:00
|
|
|
Feature_xml 0
|
|
|
|
|
#
|
|
|
|
|
# Feature GIS
|
|
|
|
|
#
|
|
|
|
|
CREATE TABLE t1 (g POINT);
|
|
|
|
|
SHOW FIELDS FROM t1;
|
|
|
|
|
Field Type Null Key Default Extra
|
|
|
|
|
g point YES NULL
|
|
|
|
|
INSERT INTO t1 VALUES
|
|
|
|
|
(PointFromText('POINT(10 10)')),
|
|
|
|
|
(PointFromText('POINT(20 10)')),
|
|
|
|
|
(PointFromText('POINT(20 20)')),
|
|
|
|
|
(PointFromWKB(AsWKB(PointFromText('POINT(10 20)'))));
|
|
|
|
|
drop table t1;
|
|
|
|
|
show status like "feature_gis";
|
|
|
|
|
Variable_name Value
|
|
|
|
|
Feature_gis 3
|
|
|
|
|
#
|
|
|
|
|
# Feature dynamic columns
|
|
|
|
|
#
|
|
|
|
|
set @a= COLUMN_CREATE(1, 1212 AS int);
|
|
|
|
|
set @b= column_add(@a, 2, 1212 as integer);
|
|
|
|
|
select column_get(@b, 2 as integer);
|
|
|
|
|
column_get(@b, 2 as integer)
|
|
|
|
|
1212
|
|
|
|
|
show status like "feature_dynamic_columns";
|
|
|
|
|
Variable_name Value
|
|
|
|
|
Feature_dynamic_columns 2
|
|
|
|
|
#
|
|
|
|
|
# Feature fulltext
|
|
|
|
|
#
|
|
|
|
|
CREATE TABLE t1 (a VARCHAR(200), b TEXT, FULLTEXT (a,b)) engine=myisam;
|
|
|
|
|
INSERT INTO t1 VALUES('MySQL has now support', 'for full-text search'),
|
|
|
|
|
('Full-text indexes', 'are called collections'),
|
|
|
|
|
('Only MyISAM tables','support collections'),
|
|
|
|
|
('Function MATCH ... AGAINST()','is used to do a search'),
|
|
|
|
|
('Full-text search in MySQL', 'implements vector space model');
|
|
|
|
|
select * from t1 where MATCH(a,b) AGAINST ("collections");
|
|
|
|
|
a b
|
|
|
|
|
Only MyISAM tables support collections
|
|
|
|
|
Full-text indexes are called collections
|
|
|
|
|
select * from t1 where MATCH(a,b) AGAINST ("indexes");
|
|
|
|
|
a b
|
|
|
|
|
Full-text indexes are called collections
|
|
|
|
|
drop table t1;
|
|
|
|
|
show status like "feature_fulltext";
|
|
|
|
|
Variable_name Value
|
|
|
|
|
Feature_fulltext 2
|
|
|
|
|
#
|
|
|
|
|
# Feature locale
|
|
|
|
|
#
|
|
|
|
|
SET lc_messages=sr_RS;
|
|
|
|
|
SET lc_messages=en_US;
|
|
|
|
|
show status like "feature_locale";
|
|
|
|
|
Variable_name Value
|
|
|
|
|
Feature_locale 2
|
|
|
|
|
#
|
|
|
|
|
# Feature subquery
|
|
|
|
|
#
|
|
|
|
|
select (select 2);
|
|
|
|
|
(select 2)
|
|
|
|
|
2
|
|
|
|
|
SELECT (SELECT 1) UNION SELECT (SELECT 2);
|
|
|
|
|
(SELECT 1)
|
|
|
|
|
1
|
|
|
|
|
2
|
|
|
|
|
create table t1 (a int);
|
|
|
|
|
insert into t1 values (2);
|
|
|
|
|
select (select a from t1 where t1.a=t2.a), a from t1 as t2;
|
|
|
|
|
(select a from t1 where t1.a=t2.a) a
|
|
|
|
|
2 2
|
|
|
|
|
drop table t1;
|
|
|
|
|
show status like "feature_subquery";
|
|
|
|
|
Variable_name Value
|
|
|
|
|
Feature_subquery 4
|
|
|
|
|
#
|
|
|
|
|
# Feature timezone
|
|
|
|
|
#
|
|
|
|
|
SELECT FROM_UNIXTIME(unix_timestamp()) > "1970-01-01";
|
|
|
|
|
FROM_UNIXTIME(unix_timestamp()) > "1970-01-01"
|
|
|
|
|
1
|
|
|
|
|
set time_zone="+03:00";
|
|
|
|
|
SELECT FROM_UNIXTIME(unix_timestamp()) > "1970-01-01";
|
|
|
|
|
FROM_UNIXTIME(unix_timestamp()) > "1970-01-01"
|
|
|
|
|
1
|
|
|
|
|
set time_zone= @@global.time_zone;
|
|
|
|
|
show status like "feature_timezone";
|
|
|
|
|
Variable_name Value
|
|
|
|
|
Feature_timezone 1
|
|
|
|
|
#
|
|
|
|
|
# Feature triggers
|
|
|
|
|
#
|
|
|
|
|
create table t1 (i int);
|
|
|
|
|
# let us test some very simple trigger
|
|
|
|
|
create trigger trg before insert on t1 for each row set @a:=1;
|
|
|
|
|
set @a:=0;
|
|
|
|
|
select @a;
|
|
|
|
|
@a
|
|
|
|
|
0
|
|
|
|
|
insert into t1 values (1),(2);
|
|
|
|
|
select @a;
|
|
|
|
|
@a
|
|
|
|
|
1
|
|
|
|
|
SHOW TRIGGERS IN test like 't1';
|
|
|
|
|
Trigger Event Table Statement Timing Created sql_mode Definer character_set_client collation_connection Database Collation
|
2016-10-02 14:35:08 +02:00
|
|
|
trg INSERT t1 set @a:=1 BEFORE # root@localhost latin1 latin1_swedish_ci latin1_swedish_ci
|
2012-09-09 00:22:06 +02:00
|
|
|
drop trigger trg;
|
|
|
|
|
drop table t1;
|
|
|
|
|
show status like "%trigger%";
|
|
|
|
|
Variable_name Value
|
2015-04-20 14:23:55 +02:00
|
|
|
Binlog_group_commit_trigger_count 0
|
|
|
|
|
Binlog_group_commit_trigger_lock_wait 0
|
|
|
|
|
Binlog_group_commit_trigger_timeout 0
|
2012-09-09 00:22:06 +02:00
|
|
|
Com_create_trigger 1
|
|
|
|
|
Com_drop_trigger 1
|
|
|
|
|
Com_show_create_trigger 0
|
|
|
|
|
Com_show_triggers 1
|
|
|
|
|
Executed_triggers 2
|
|
|
|
|
Feature_trigger 2
|
|
|
|
|
#
|
|
|
|
|
# Feature xml
|
|
|
|
|
#
|
|
|
|
|
SET @xml='<a aa1="aa1" aa2="aa2">a1<b ba1="ba1">b1<c>c1</c>b2</b>a2</a>';
|
|
|
|
|
SELECT extractValue(@xml,'/a');
|
|
|
|
|
extractValue(@xml,'/a')
|
|
|
|
|
a1 a2
|
|
|
|
|
select updatexml('<div><div><span>1</span><span>2</span></div></div>',
|
|
|
|
|
'/','<tr><td>1</td><td>2</td></tr>') as upd1;
|
|
|
|
|
upd1
|
|
|
|
|
<tr><td>1</td><td>2</td></tr>
|
|
|
|
|
show status like "feature_xml";
|
|
|
|
|
Variable_name Value
|
|
|
|
|
Feature_xml 2
|
2014-07-19 16:46:08 +02:00
|
|
|
#
|
|
|
|
|
# Feature delayed_keys
|
|
|
|
|
#
|
|
|
|
|
create table t1 (a int, key(a)) engine=myisam delay_key_write=1;
|
|
|
|
|
insert into t1 values(1);
|
|
|
|
|
insert into t1 values(2);
|
|
|
|
|
drop table t1;
|
|
|
|
|
create table t1 (a int, key(a)) engine=aria delay_key_write=1;
|
|
|
|
|
insert into t1 values(1);
|
|
|
|
|
insert into t1 values(2);
|
|
|
|
|
drop table t1;
|
|
|
|
|
show status like "feature_delay_key_write";
|
|
|
|
|
Variable_name Value
|
|
|
|
|
Feature_delay_key_write 2
|
2016-07-25 22:15:05 +02:00
|
|
|
create table t1 (a int check (a > 5));
|
|
|
|
|
create table t2 (b int, constraint foo check (b < 10));
|
|
|
|
|
drop table t1, t2;
|
|
|
|
|
show status like "feature_check_constraint";
|
|
|
|
|
Variable_name Value
|
|
|
|
|
Feature_check_constraint 2
|