Details
-
Bug
-
Status: Open (View Workflow)
-
Critical
-
Resolution: Unresolved
-
12.3
-
None
Description
Following our convention with the json data type, we should be pushing an addition extended metadata format=xml for the xml data type in the protocol so the receiving end knows its xml.
|
--column-type-info |
MariaDB [test]> CREATE TABLE t1(id INT, x xmltype);
|
Query OK, 0 rows affected (0.001 sec)
|
|
|
MariaDB [test]> INSERT INTO t1 VALUES (1, '<one></one>'), (2, '<two></two>'), (3, '<three></three>');
|
Query OK, 3 rows affected (0.001 sec)
|
Records: 3 Duplicates: 0 Warnings: 0
|
|
|
MariaDB [test]> select x from t1;
|
Field 1: `x`
|
Org_field: `x`
|
Catalog: `def`
|
Database: `test`
|
Table: `t1`
|
Org_table: `t1`
|
Type: BLOB
|
Collation: utf8mb4_unicode_ci (224)
|
Length: 4294967295
|
Max_length: 15
|
Decimals: 0
|
Flags: BLOB
|
|
|
|
|
+-----------------+
|
| x |
|
+-----------------+
|
| <one></one> |
|
| <two></two> |
|
| <three></three> |
|
+-----------------+
|
3 rows in set (0.001 sec)
|
If it was JSON, Type would be BLOB (format=json)
Attachments
Issue Links
- is caused by
-
MDEV-37261 Basic XML data type
-
- Closed
-