[#MDEV-9316] Add Field::store_hex

depends on the data type. It should be split apart into virtual methods in Field, so the user-defined data types and the standard data types look similar.

For example, the INET6 data type will need its own conversion, which is not compatible with the current behavior of Item_hex_hybrid::save_in_field().

-int Item_hex_hybrid::save_in_field(Field *field, bool no_conversions)

+int Item_hex_hybrid::save_in_field_as_string(Field *field)

   field->set_notnull();

-  if (field->result_type() == STRING_RESULT)

-    return field->store(str_value.ptr(), str_value.length(),

-                        collation.collation);

+  return field->store(str_value.ptr(), str_value.length(),

+                      collation.collation);

+}

+int Item_hex_hybrid::save_in_field_as_number(Field *field)

+{

+  field->set_notnull();

@@ -6413,6 +6466,15 @@ int Item_hex_hybrid::save_in_field(Field

+int Item_hex_hybrid::save_in_field(Field *field, bool no_conversions)

+{

+  if (const Type_handler *handler= Type_handlers.handler(field->type()))

+    return handler->save_in_field(this, field);

+  return field->result_type() == STRING_RESULT ?

+         save_in_field_as_string(field) : save_in_field_as_number(field);

+}

[MDEV-9316] Add Field::store_hex_hybrid() Created: 2015-12-23 Updated: 2016-01-12 Resolved: 2016-01-12
Status:	Closed
Project:	MariaDB Server
Component/s:	OTHER
Fix Version/s:	10.2.0

[MDEV-9316] Add Field::store_hex_hybrid() Created: 2015-12-23 Updated: 2016-01-12 Resolved: 2016-01-12