column type 'geometry' is not recognized by column_info [rt.cpan.org #118751] #206
Description
Migrated from rt.cpan.org#118751 (status was 'open')
Requestors:
Attachments:
From [email protected] on 2016-11-14 01:35:03:
Whenever I call $dbh->column_info on a table that contains a column of type 'geometry', the following warning is printed:
column_info: unrecognized column type 'geometry' of `pbdb`.`collections`.coordinate treated as varchar
This despite the fact that 'geometry' is a recognized column type in MySQL. These messages are littering my error logs. Can you please make them go away?
One obvious solution is to silently treat a column of type GEOMETRY as VARCHAR.
-- Michael McClennen
From [email protected] on 2016-11-19 20:25:40:
On Ned Nov 13 20:35:03 2016, [email protected] wrote:
> Whenever I call $dbh->column_info on a table that contains a column of
> type 'geometry', the following warning is printed:
>
> column_info: unrecognized column type 'geometry' of
> `pbdb`.`collections`.coordinate treated as varchar
>
> This despite the fact that 'geometry' is a recognized column type in
> MySQL. These messages are littering my error logs. Can you please
> make them go away?
>
> One obvious solution is to silently treat a column of type GEOMETRY as
> VARCHAR.
>
> -- Michael McClennen
Can you try attached patch?
From [email protected] on 2016-11-20 09:30:41:
On Sat 19 Nov 2016 15:25:40, PALI wrote:
> On Ned Nov 13 20:35:03 2016, [email protected] wrote:
> > Whenever I call $dbh->column_info on a table that contains a column of
> > type 'geometry', the following warning is printed:
> >
> > column_info: unrecognized column type 'geometry' of
> > `pbdb`.`collections`.coordinate treated as varchar
> >
> > This despite the fact that 'geometry' is a recognized column type in
> > MySQL. These messages are littering my error logs. Can you please
> > make them go away?
>
> Can you try attached patch?
Hi Pali,
please note we also have a similar ticket https://rt.cpan.org/Ticket/Display.html?id=117846 about the 'json' type.
I think we should check all more 'recent' data types in MySQL and add them.
For instance, this page:
https://dev.mysql.com/doc/refman/5.7/en/spatial-datatypes.html
lists apart from 'geometry' also
POINT
LINESTRING
POLYGON
MULTIPOINT
MULTILINESTRING
MULTIPOLYGON
GEOMETRYCOLLECTION
And there are probably loads more non-spatial datatypes we don't support.
What are your ideas on this?
--
Michiel
From [email protected] on 2016-11-20 12:37:56:
On Ned Nov 20 04:30:41 2016, MICHIELB wrote:
> What are your ideas on this?
IIRC mysql can handle any type via string/varchar. If there are really no exception, then we can easily handle all those unsupported types as string/varchar/blob without any problems. But it is needed to recheck if this is still truth.