summaryrefslogtreecommitdiff
path: root/storage/innobase/data
diff options
context:
space:
mode:
authorSatya B <satya.bn@sun.com>2009-11-30 14:23:52 +0530
committerSatya B <satya.bn@sun.com>2009-11-30 14:23:52 +0530
commit2df31d44e14976291fdb7383af9dcd97122a3eae (patch)
tree5975a1cc7e3d2be542a5a3c8b14474b1b185ecc6 /storage/innobase/data
parent3431bede10e13eac085482b004aead4d4640ecfc (diff)
downloadmariadb-git-2df31d44e14976291fdb7383af9dcd97122a3eae.tar.gz
Applying InnoDB snapshot 5.1-ss6242, part 4. Fixes BUG#48526
1. BUG#48526 - Data type for float and double is incorrectly reported in InnoDB table monitor Detailed revision comments: r6188 | jyang | 2009-11-18 07:14:23 +0200 (Wed, 18 Nov 2009) | 8 lines branches/5.1: Fix bug #48526 "Data type for float and double is incorrectly reported in InnoDB table monitor". Certain datatypes are not printed correctly in dtype_print(). rb://204 Approved by Marko.
Diffstat (limited to 'storage/innobase/data')
-rw-r--r--storage/innobase/data/data0type.c16
1 files changed, 16 insertions, 0 deletions
diff --git a/storage/innobase/data/data0type.c b/storage/innobase/data/data0type.c
index 305000d7c0a..a3cfe691404 100644
--- a/storage/innobase/data/data0type.c
+++ b/storage/innobase/data/data0type.c
@@ -252,6 +252,22 @@ dtype_print(
fputs("DATA_SYS", stderr);
break;
+ case DATA_FLOAT:
+ fputs("DATA_FLOAT", stderr);
+ break;
+
+ case DATA_DOUBLE:
+ fputs("DATA_DOUBLE", stderr);
+ break;
+
+ case DATA_DECIMAL:
+ fputs("DATA_DECIMAL", stderr);
+ break;
+
+ case DATA_VARMYSQL:
+ fputs("DATA_VARMYSQL", stderr);
+ break;
+
default:
fprintf(stderr, "type %lu", (ulong) mtype);
break;