How to efficiently determine changes between rows using SQL

mysql, optimization, query-optimization, sql

Solution

You might try this - I'm not going to guarantee that it will perform better, but it's my usual way of correlating a row with a "previous" row:

SELECT
    * --TODO, list columns
FROM
    data d
       left join
    data d_prev
       on
           d_prev.time < d.time --TODO - Other key columns?
       left join
    data d_inter
       on
           d_inter.time < d.time and
           d_prev.time < d_inter.time --TODO - Other key columns?
WHERE
    d_inter.time is null AND
    (d_prev.value is null OR d_prev.value <> d.value)

(I think this is right - could do with some sample data to validate it).

Basically, the idea is to join the table to itself, and for each row (in `d`), find candidate rows (in `d_prev`) for the "previous" row. Then do a further join, to try to find a row (in `d_inter`) that exists between the current row (in `d`) and the candidate row (in `d_prev`). If we cannot find such a row (`d_inter.time is null`), then that candidate was indeed the previous row.

Problem

I have a very large MySQL table containing data read from a number of sensors. Essentially, there's a time stamp and a value column. I'll omit the sensor id, indexes other details here: ``` CREATE TABLE `data` ( `time` datetime NOT NULL, `value` float NOT NULL ) ``` The `value` column rarely changes, and I need to find the points in time when those changes occur. Suppose there's a value every minute, the following query returns exactly what I need: ``` SELECT d.*, (SELECT value FROM data WHERE time<d.time ORDER by time DESC limit 1) AS previous_value FROM data d HAVING d.value<>previous_value OR previous_value IS NULL; +---------------------+-------+----------------+ | time | value | previous_value | +---------------------+-------+----------------+ | 2011-05-23 16:05:00 | 1 | NULL | | 2011-05-23 16:09:00 | 2 | 1 | | 2011-05-23 16:11:00 | 2.5 | 2 | +---------------------+-------+----------------+ ``` The only problem is that this is very inefficient, mostly due to the dependent subquery. What would be the best way to optimize this using the tools that MySQL 5.1 has to offer? One last constraint is that the values are not ordered before they are inserted into the data table and that they might be updated at a later point. This might affect any possible de-normalization strategies.

Original source