WL#3691: NDB API needs to have native data types extended to match MySQL
Affects: Server-7.1 — Status: Un-Assigned — Priority: Medium
NDB API NdbRecAttr is missing some of the native data types that are supported by MySQL in general. The API interface should be expanded to allow these types to be used in an API application without the need of extra work on the customer part. Missing: NdbRecAttr::DECIMAL NdbRecAttr::DATETIME NdbRecAttr::DATE NdbRecAttr::TIMESTAMP NdbRecAttr::TIME NdbRecAttr::YEAR NdbRecAttr::VARCHAR NdbRecAttr::BINARY NdbRecAttr::VARBINARY NDB Team may want to consider MySQL Spatial Data Types MySQL has data types that correspond to OpenGIS classes. Some of these types hold single geometry values: * GEOMETRY * POINT * LINESTRING * POLYGON GEOMETRY can store geometry values of any type. The other single-value types (POINT, LINESTRING, and POLYGON) restrict their values to a particular geometry type. The other data types hold collections of values: * MULTIPOINT * MULTILINESTRING * MULTIPOLYGON * GEOMETRYCOLLECTION GEOMETRYCOLLECTION can store a collection of objects of any type. The other collection types (MULTIPOINT, MULTILINESTRING, MULTIPOLYGON, and GEOMETRYCOLLECTION) restrict collection members to those having a particular geometry type. PekkaNousiainen - Thu, 18 Jan 2007, 00:30) NdbRecAttr is only for selected attributes. Need similar support for insert/update/delete values and keys (pk, index). Does this fit somewhere around NdbRecord?
Copyright (c) 2000, 2017, Oracle Corporation and/or its affiliates. All rights reserved.