Wrong parameter type for `GEOMETRY` columns

[bobozaur]

Create a table:

CREATE TABLE my_table (geo GEOMETRY);

Prepare an insert statement:

INSERT INTO my_table VALUES (?);

The expected type for the parameter would be GEOMETRY(0), yet VARCHAR(2000000) UTF8 is returned instead. A SELECT statement returns the correct GEOMETRY type for the result set columns, though.

I understand that this might've been chosen because GEOMETRY types are constructed from strings, yet the same could be said about HASHTYPE which instead consistently returns the correct type for both result sets columns and prepared statement parameters.

I think that ideally the same behavior should be employed for GEOMETRY columns for consistency.

Tested with the Docker containers for versions 7.0.22 and 8.29.11

[exazg]

This is currently how it is intended to work. It may change or be handled differently in the future, but there's currently no plan to do so. By the way, this behavior is not specific to the WebSocket API. All of the drivers handle the metadata type information similarly.