Thanks Ian! That will help a lot. I look forward to your updates. -- Michael Moore On Wed, May 25, 2016 at 5:43 AM, Ian Gilfillan wrote:

Hi Michael

Great, thanks for the initiative!

Unfortunately, most of the function pages don't specify the version they were introduced. They should all do so, as on https://mariadb.com/kb/en/mariadb/st-within/ and https://mariadb.com/kb/en/mariadb/st_boundary/ for example. The ones that don't mention the version are the older articles, so for early versions of MariaDB.

I'll look at adding this version information to the pages in the next few days, and then you can base your table on that.

On 25/05/2016 07:31, Michael Moore wrote:

...

Hi,

I'm trying to put together a table of which spatial functions are supported by MySQL and MariaDB at which version numbers.

Something like https://dev.mysql.com/doc/refman/5.5/en/spatial-function-reference.html for different versions would be awesome, but I can't find it.

Checking wiki history isn't very helpful because it just shows a date that it was changed, with no mention of why.

Is there a better approach I could be taking?

I'm making the table for WordPress plugin developers, who have to deal with sometimes old versions of MySQL and MariaDB on their hosts without control over the upgrade schedule.

Once I have the table compiled I'd love to share it back on the MariaDB KB for future people looking for the same thing.

Many thanks, Michael Moore

_______________________________________________ Mailing list: https://launchpad.net/~maria-docs Post to : maria-docs@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-docs More help : https://help.launchpad.net/ListHelp

Thanks Ian, I've started going through the functions. On https://mariadb.com/kb/en/mariadb/st_convexhull/, the note says "ST_ConvexHull() was introduced in MariaDB 10.1.2" -- per your last email, it sounds like that means that ConvexHull (no ST_) should've been in MariaDB in all versions. Since MySQL didn't add ConvexHull until 5.7.5, I'm wondering if - I'm misinterpreting that, - MariaDB really did have ConvexHull since the start - MySQL's docs are off and it did have it previously - MariaDB's docs are off and ConvexHull was also added in 10.1.2 Also, MySQL 5.7.6 deprecated several functions, including ConvexHull() -- are any functions currently deprecated in MariaDB, and if so, are they noted as such? Or would that come in a future version? Once again, thanks for your help! -- Michael Moore On Fri, May 27, 2016 at 8:43 AM, Ian Gilfillan wrote:

Hi Michael

The versions have been added to the function documentation.

If no version is listed, it's available in all versions of MariaDB, for example https://mariadb.com/kb/en/mariadb/glength/

Some have had synonyms added, for example https://mariadb.com/kb/en/mariadb/st_geomcollfromwkb/ where GeomCollFromWKB is available in all versions, and ST_GeomCollFromWKB since 5.3.3

Looking forward to seeing the table!

On 25/05/2016 14:35, Michael Moore wrote:

Thanks Ian!

That will help a lot.

I look forward to your updates.

-- Michael Moore

On Wed, May 25, 2016 at 5:43 AM, Ian Gilfillan wrote:

...

Hi Michael

Great, thanks for the initiative!

Unfortunately, most of the function pages don't specify the version they were introduced. They should all do so, as on https://mariadb.com/kb/en/mariadb/st-within/ https://mariadb.com/kb/en/mariadb/st-within/ and https://mariadb.com/kb/en/mariadb/st_boundary/ for example. The ones that don't mention the version are the older articles, so for early versions of MariaDB.

I'll look at adding this version information to the pages in the next few days, and then you can base your table on that.

On 25/05/2016 07:31, Michael Moore wrote:

...

Hi,

I'm trying to put together a table of which spatial functions are supported by MySQL and MariaDB at which version numbers.

Something like https://dev.mysql.com/doc/refman/5.5/en/spatial-function-reference.html for different versions would be awesome, but I can't find it.

Checking wiki history isn't very helpful because it just shows a date that it was changed, with no mention of why.

Is there a better approach I could be taking?

I'm making the table for WordPress plugin developers, who have to deal with sometimes old versions of MySQL and MariaDB on their hosts without control over the upgrade schedule.

Once I have the table compiled I'd love to share it back on the MariaDB KB for future people looking for the same thing.

Many thanks, Michael Moore

_______________________________________________ Mailing list: https://launchpad.net/~maria-docs Post to : maria-docs@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-docs More help : https://help.launchpad.net/ListHelp

I've got the table compiled here. https://docs.google.com/spreadsheets/d/1R7vwdctsoGQADY9i24yArvz8wQ59GSr59wKY... Would it be appropriate to add it to the KB? I was going to put it on our company blog, but since new versions will bring new features it should probably be a living document somewhere. The only reason I could think of that it might not be appropriate on the KB is that I do include the MySQL info too, and I'm not sure if that belongs on the MariaDB wiki. Also, two more questions: - How long has the Aria database had spatial index support? Since MariaDB 5.1? - I didn't see docs for X() and Y(), but they were in MySQL since 5.4 so I suspect that they're probably in MariaDB too. Thanks! Michael Moore On Sat, May 28, 2016 at 3:57 AM, Ian Gilfillan wrote:

No, both were introduced in 10.1.2. In most cases, this is the wording that is used, and all synonyms are assumed to be introduced at the same time. Only in the case of the ST_ synonym being introduced at a different time does the text state "... introduced as a synonym in version ...". So unless specified, assume in cases like these that both arrived at the given version.

As for deprecated functions, assume they're not unless specified, but it's possible something has been overlooked. I know in the past features have been deprecated with a small note in the code, and this has never made it to the documentation. ConvexHull does not appear to be deprecated though.

On 28/05/2016 06:53, Michael Moore wrote:

...

Thanks Ian, I've started going through the functions.

On https://mariadb.com/kb/en/mariadb/st_convexhull/, the note says "ST_ConvexHull() was introduced in MariaDB 10.1.2" -- per your last email, it sounds like that means that ConvexHull (no ST_) should've been in MariaDB in all versions.

Since MySQL didn't add ConvexHull until 5.7.5, I'm wondering if

* I'm misinterpreting that, * MariaDB really did have ConvexHull since the start * MySQL's docs are off and it did have it previously * MariaDB's docs are off and ConvexHull was also added in 10.1.2

Also, MySQL 5.7.6 deprecated several functions, including ConvexHull() -- are any functions currently deprecated in MariaDB, and if so, are they noted as such? Or would that come in a future version?

Once again, thanks for your help!

On 28/05/2016 17:30, Michael Moore wrote:

I've got the table compiled here.

https://docs.google.com/spreadsheets/d/1R7vwdctsoGQADY9i24yArvz8wQ59GSr59wKY...

The table is proving useful in spotting some oversights in the MariaDB documentation! The CENTROID function exists (but has no article in the MariaDB docs). I also want to look into a few other cases, which may just be missing from the MariaDB documentation. Besides X() and Y(), Area is listed as missing in MariaDB, but is present - https://mariadb.com/kb/en/mariadb/st_area/

On 30/05/2016 20:25, Michael Moore wrote:

I've updated X(),Y(), Centroid() and Area and created a page in the KB here: https://mariadb.com/kb/en/mariadb/mysqlmariadb-spatial-support-matrix/

I couldn't get the color markup to work correctly. When I used the syntax listed here (http://wiki.wikicreole.org/HelpOnTables) it just printed the <bgcolor> and <style> tags. I'd be happy to color the table if you can tell me what syntax to use.

I've added some color on the page with the style macro (thanks Bryan for pointing it out) - https://mariadb.com/kb/en/meta/the-style-macro/ - it's very clunky, with miles of styles, but we can look at adding some generic classes for use in similar tables in future.