From 56ff6f1b0b248befb80675ba36a3251c7844f410 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marko=20M=C3=A4kel=C3=A4?= Date: Mon, 3 Jul 2017 11:47:54 +0300 Subject: 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. --- storage/innobase/data/data0type.cc | 8 -------- 1 file changed, 8 deletions(-) (limited to 'storage/innobase/data') diff --git a/storage/innobase/data/data0type.cc b/storage/innobase/data/data0type.cc index a40724b303d..d4b809c3f59 100644 --- a/storage/innobase/data/data0type.cc +++ b/storage/innobase/data/data0type.cc @@ -193,14 +193,6 @@ dtype_print(const dtype_t* type) fputs("DATA_BLOB", stderr); break; - case DATA_POINT: - fputs("DATA_POINT", stderr); - break; - - case DATA_VAR_POINT: - fputs("DATA_VAR_POINT", stderr); - break; - case DATA_GEOMETRY: fputs("DATA_GEOMETRY", stderr); break; -- cgit v1.2.1