Marko Mäkelä 56ff6f1b0b InnoDB: Remove dead code for DATA_POINT and DATA_VAR_POINT ... The POINT data type is being treated just like any other geometry data type in InnoDB. The fixed-length data type DATA_POINT had been introduced in WL#6942 based on a misunderstanding and without appropriate review. Because of fundamental design problems (such as a DEFAULT POINT(0 0) value secretly introduced by InnoDB), the code was disabled in Oracle Bug#20415831 fix. This patch removes the dead code and definitions that were left behind by the Oracle Bug#20415831 patch.		2017-07-03 12:17:10 +03:00
..
ha_innodb.cc	InnoDB: Remove dead code for DATA_POINT and DATA_VAR_POINT	2017-07-03 12:17:10 +03:00
ha_innodb.h	Remove the unnecessary method handlerton::release_temporary_latches()	2017-06-16 12:37:00 +03:00
ha_innopart.cc	Remove trx_t::has_search_latch and simplify debug code	2017-06-16 13:17:05 +03:00
ha_innopart.h	Bug #23046302 COUNT(*) MUCH SLOWER ON 5.7 THAN 5.6	2017-04-26 23:03:33 +03:00
ha_xtradb.h	Fix of emulated variables comments to reflect reality.	2017-05-10 11:08:33 +02:00
handler0alter.cc	InnoDB: Remove dead code for DATA_POINT and DATA_VAR_POINT	2017-07-03 12:17:10 +03:00
handler0alter_innopart.cc	Merge InnoDB 5.7 from mysql-5.7.9.	2016-09-02 13:22:28 +03:00
i_s.cc	Remove trx_t::has_search_latch and simplify debug code	2017-06-16 13:17:05 +03:00
i_s.h	Merge 10.1 into 10.2	2017-05-22 09:46:51 +03:00