Re: [Geotools-devel] MySQL 8.0 spatial functions name change bug

2020-10-28 Thread Nikolaos Pringouris
Hi, Indeed the usage of mysql for spatial data handling was rather limited some years ago mainly to the fact that until v5.5 spatial support was rather limited to working with minimum bounding rectangles rather than the actual geometries and spatial functions provided quite limited. However since

Re: [Geotools-devel] MySQL 8.0 spatial functions name change bug

2020-10-28 Thread Andrea Aime
On Wed, Oct 28, 2020 at 3:46 PM Martin Baxter via GeoTools-Devel < geotools-devel@lists.sourceforge.net> wrote: > I'm glad you sometimes get an itch to make progress on this. I read that > MySQL is the second-most popular database, As a generic relational database that might be still true, but w

Re: [Geotools-devel] MySQL 8.0 spatial functions name change bug

2020-10-28 Thread Martin Baxter via GeoTools-Devel
ishes, Martin -- Original Message -- From: "mark" To: geotools-devel@lists.sourceforge.net Sent: 28-Oct-2020 10:02:15 Subject: Re: [Geotools-devel] MySQL 8.0 spatial functions name change bug As the doc [https://docs.geoserver.org/latest/en/user/data/database/mysql.html] s

Re: [Geotools-devel] MySQL 8.0 spatial functions name change bug

2020-10-28 Thread mark
As the doc [https://docs.geoserver.org/latest/en/user/data/database/mysql.html] says MySQL is an unmaintained and unsupported extension in GeoServer, basically that means it gets worked on when someone receives an incentive or gets an itch. To scratch my itch I've started working on MySQL 8 s

[Geotools-devel] MySQL 8.0 spatial functions name change bug

2020-10-27 Thread Martin Baxter via GeoTools-Devel
Dear GeoTools developers, I'm new to your project but have been using GeoServer happily for several years. I tried a recent upgrade to MySQL 8.0 and discovered that the MySQL team have made some non-backwards compatible changes which have broken GeoTools. That's a shame since MySQL 8 has b