Mathias Gaunard wrote:

On 01/04/14 23:45, Barend Gehrels wrote:

...

Hi,

Recent news which is published this week (actually today): Boost.Geometry will be used for MySQL 's spatial database features.

http://mysqlserverteam.com/building-mysql-with-boost/

This also means MySQL (server) will now use Boost libraries from now on.

Regards, Barend

Nice!

This is getting me interested in Boost.Geometry's spatial indexes.

FYI, MySQL is using its own implementation of spatial index :) Regards, Adam

On 3 April 2014 14:46, Mathias Gaunard <mathias.gaunard@ens-lyon.org> wrote:

On 02/04/14 17:02, Adam Wulkiewicz wrote:

...

Mathias Gaunard wrote:

...

On 01/04/14 23:45, Barend Gehrels wrote:

...

Recent news which is published this week (actually today): Boost.Geometry will be used for MySQL 's spatial database features.

http://mysqlserverteam.com/building-mysql-with-boost/

This also means MySQL (server) will now use Boost libraries from now on.

Regards, Barend

Nice!

This is getting me interested in Boost.Geometry's spatial indexes.

FYI, MySQL is using its own implementation of spatial index :)

So what are they using Boost.Geometry for

Algorithms, presumably, with adapting their in-house geometry models.

and if they're using it, why not go as far as to use the spatial index?

I *guess*, somewhat based on reading MariaDB code, it is because of data structure differences and the fact indexing is tightly coupled MySQL engine used in an instance. AFAIK, Boost.Geometry-enabled MySQL will be released along its source code, then it will be easier to analyse and test it. I'm personally looking forward to checking it and trying it out. Best regards, -- Mateusz Łoskot, http://mateusz.loskot.net