Transforming GPS coordinates into trajectories in MySQL involves organizing raw GPS points (as POINT geometries) into ordered paths and converting them into LINESTRING geometries. This process uses MySQL's spatial functions like ST_Collect to aggregate points and requires ensuring proper ordering (e.g., by timestamp or sequence) to construct accurate routes.

This blog post explores how to transform spatial data between different Spatial Reference Systems (SRS) in MySQL using the ST_Transform function. It covers the syntax and usage of ST_Transform, and its practical applications in mapping and spatial analysis by using demonstrative examples. Whether you're visualizing geographic data or integrating datasets from various sources, understanding SRS transformation is key to accurate spatial analysis.

MySQL 9.2.0 has introduced a new dynamic privilege: CREATE_SPATIAL_REFERENCE_SYSTEM. This privilege enables users to create, replace, and drop custom spatial reference systems (SRS), allowing for greater spatial data customization across MySQL environments without needing SUPER access. In this post, we’ll explain the use of this privilege and provide an example to demonstrate its application. The new privilege is available in MySQL Community and Enterprise Editions and HeatWave MySQL.

The MySQL Connection-Control Component allows database administrators to enforce limits on client connections based on frequency and behavior. It is especially useful in preventing denial-of-service (DoS) attacks, mitigating resource exhaustion, and regulating access during high-load scenarios.

What index will be used when you count all rows in a table? Well, the MySQL documentation provides a straightforward answer to this, quoting: InnoDB processes SELECT COUNT(*) statements by traversing the smallest available secondary index unless an index or optimizer hint directs the optimizer to use a different index. If a secondary index is […]

In reply to John.

Not sure about the seg fault on docker. If I were you, I’d open another bug for that. As for the ANSI mode, it’s a drupal thing apparently, as per https://www.drupal.org/node/344575. Other than forcing sql_mode on each user to be specific, and even then I believe they set it at session level anyhow, I suspect we’ll just have to wait for it to be fixed in router v9.0 or similar. In order to help with that, maybe you could also open a bug against the same issue and help pressure the Router dev team? The more the merrier….

LikeLike …

Thanks Keith,

I’m having same trouble with MySQL Router 8.3 and drupal. sql_mode is set to ANSI

and MYSQL_ATTR_USE_BUFFERED_QUERY is ON.

Strangly Drupal 8.5 changed to ANSI_QUOTES

https://git.drupalcode.org/project/drupal/-/blame/10.5.x/core/modules/mysql/src/Driver/Database/mysql/Connection.php?ref_type=heads#L94

After a while, the router crash with a seg fault on docker.

LikeLike

MySQL January 2025 GA Releases Now Available