Databases
StackOverflow2013
Postsdbo
POAggregate dates from multiple rows into one
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POAggregate dates from multiple rows into one
    primarykey
    data
    text
    <p>I have a table that stores GPS coordinates at events (like rock concerts).</p> <p>It looks like this:</p> <pre><code>sequence | event_id | location_id | device_number | timestamp | latitude | longitude | event -------------------------------------------------------------------------------------------------------------------------------- 1 | 101 | 2201 | 220 | 2013-10-29 05:01:00 | 37.757196 | -122.441681 | enter 2 | 101 | 2202 | 220 | 2013-10-29 05:02:00 | 37.757196 | -122.441681 | NULL 3 | 101 | 2203 | 220 | 2013-10-29 05:03:00 | 37.757196 | -122.441681 | NULL 4 | 101 | 2204 | 220 | 2013-10-29 05:04:00 | 37.757196 | -122.441681 | NULL 5 | 101 | 2205 | 220 | 2013-10-29 05:05:00 | 37.757196 | -122.441681 | NULL 6 | 101 | 2206 | 220 | 2013-10-29 05:06:00 | 37.757196 | -122.441681 | NULL 7 | 101 | 2207 | 220 | 2013-10-29 05:07:00 | 37.757196 | -122.441681 | exit 8 | 102 | 2208 | 220 | 2013-10-29 05:08:00 | 38.865221 | -123.920201 | enter 9 | 102 | 2209 | 220 | 2013-10-29 05:09:00 | 38.865221 | -123.920201 | NULL 10 | 102 | 2210 | 220 | 2013-10-29 05:10:00 | 38.865221 | -123.920201 | NULL 11 | 102 | 2211 | 220 | 2013-10-29 05:11:00 | 38.865221 | -123.920201 | NULL 12 | 102 | 2212 | 220 | 2013-10-29 05:12:00 | 38.865221 | -123.920201 | NULL 13 | 102 | 2213 | 220 | 2013-10-29 05:13:00 | 38.865221 | -123.920201 | NULL 14 | 102 | 2214 | 220 | 2013-10-29 05:14:00 | 38.865221 | -123.920201 | exit 15 | 101 | 2215 | 220 | 2013-10-29 05:15:00 | 37.757196 | -122.441681 | enter 16 | 101 | 2216 | 220 | 2013-10-29 05:16:00 | 37.757196 | -122.441681 | NULL 17 | 101 | 2217 | 220 | 2013-10-29 05:17:00 | 37.757196 | -122.441681 | NULL 18 | 101 | 2218 | 220 | 2013-10-29 05:18:00 | 37.757196 | -122.441681 | NULL 19 | 101 | 2219 | 220 | 2013-10-29 05:19:00 | 37.757196 | -122.441681 | NULL 20 | 101 | 2220 | 220 | 2013-10-29 05:20:00 | 37.757196 | -122.441681 | NULL 21 | 101 | 2221 | 220 | 2013-10-29 05:21:00 | 37.757196 | -122.441681 | exit 22 | 101 | 2222 | 330 | 2013-10-29 05:15:00 | 37.757197 | -122.441682 | enter 23 | 101 | 2223 | 330 | 2013-10-29 05:16:00 | 37.757197 | -122.441682 | NULL 24 | 101 | 2224 | 330 | 2013-10-29 05:17:00 | 37.757197 | -122.441682 | NULL 25 | 101 | 2225 | 330 | 2013-10-29 05:18:00 | 37.757197 | -122.441682 | NULL 26 | 101 | 2226 | 330 | 2013-10-29 05:19:00 | 37.757197 | -122.441682 | NULL 27 | 101 | 2227 | 330 | 2013-10-29 05:20:00 | 37.757197 | -122.441682 | exit </code></pre> <ul> <li>A <code>device_number</code> is a particular GPS device owned by user.</li> <li>The <code>event</code> column indicates when a particular GPS <code>device_number</code> walked in or out of an event_id based on their geographical coordinates.</li> </ul> <p>I would like to summarize the above data in a table called <code>billable_times</code>:</p> <pre><code>id | event_id | device_number | begin_time | end_time | duration (minutes) ---------------------------------------------------------------------------------------------- 1 | 101 | 220 | 2013-10-29 05:01:00 | 2013-10-29 05:07:00 | 6 2 | 102 | 220 | 2013-10-29 05:08:00 | 2013-10-29 05:14:00 | 6 3 | 101 | 220 | 2013-10-29 05:15:00 | 2013-10-29 05:21:00 | 6 4 | 101 | 330 | 2013-10-29 05:15:00 | 2013-10-29 05:20:00 | 5 </code></pre> <p>How could I store a range of timestamps as a single row with only the <code>begin_time</code> and <code>end_time</code>?</p> <p>Here are some helpful table creation scripts:</p> <pre><code>CREATE TABLE `intersections` ( `sequence` int(11) NOT NULL AUTO_INCREMENT, `event_id` int(11) DEFAULT NULL, `location_id` int(11) NOT NULL, `device_number` varchar(255) NOT NULL, `timestamp` datetime NOT NULL, `latitude` decimal(20,15) NOT NULL, `longitude` decimal(20,15) NOT NULL, `event` varchar(255) DEFAULT NULL, PRIMARY KEY (`sequence`), UNIQUE KEY `index_intersections_on_location_id_and_event_id` (`location_id`,`event_id`) ); INSERT INTO `intersections` (`sequence`, `event_id`, `location_id`, `device_number`, `timestamp`, `latitude`, `longitude`, `event`) VALUES (1, 101, 2201, '220', '2013-10-29 05:01:00', 37.757196, -122.441681, 'enter'), (2, 101, 2202, '220', '2013-10-29 05:02:00', 37.757196, -122.441681, NULL), (3, 101, 2203, '220', '2013-10-29 05:03:00', 37.757196, -122.441681, NULL), (4, 101, 2204, '220', '2013-10-29 05:04:00', 37.757196, -122.441681, NULL), (5, 101, 2205, '220', '2013-10-29 05:05:00', 37.757196, -122.441681, NULL), (6, 101, 2206, '220', '2013-10-29 05:06:00', 37.757196, -122.441681, NULL), (7, 101, 2207, '220', '2013-10-29 05:07:00', 37.757196, -122.441681, 'exit'), (8, 102, 2208, '220', '2013-10-29 05:08:00', 37.757196, -122.441681, 'enter'), (9, 102, 2209, '220', '2013-10-29 05:09:00', 37.757196, -122.441681, NULL), (10, 102, 2210, '220', '2013-10-29 05:10:00', 37.757196, -122.441681, NULL), (11, 102, 2211, '220', '2013-10-29 05:11:00', 37.757196, -122.441681, NULL), (12, 102, 2212, '220', '2013-10-29 05:12:00', 37.757196, -122.441681, NULL), (13, 102, 2213, '220', '2013-10-29 05:13:00', 37.757196, -122.441681, NULL), (14, 102, 2214, '220', '2013-10-29 05:14:00', 37.757196, -122.441681, 'exit'), (15, 101, 2215, '220', '2013-10-29 05:15:00', 37.757196, -122.441681, 'enter'), (16, 101, 2216, '220', '2013-10-29 05:16:00', 37.757196, -122.441681, NULL), (17, 101, 2217, '220', '2013-10-29 05:17:00', 37.757196, -122.441681, NULL), (18, 101, 2218, '220', '2013-10-29 05:18:00', 37.757196, -122.441681, NULL), (19, 101, 2219, '220', '2013-10-29 05:19:00', 37.757196, -122.441681, NULL), (20, 101, 2220, '220', '2013-10-29 05:20:00', 37.757196, -122.441681, NULL), (21, 101, 2221, '220', '2013-10-29 05:21:00', 37.757196, -122.441681, 'exit'), (22, 101, 2222, '330', '2013-10-29 05:15:00', 37.757196, -122.441681, 'enter'), (23, 101, 2223, '330', '2013-10-29 05:16:00', 37.757196, -122.441681, NULL), (24, 101, 2224, '330', '2013-10-29 05:17:00', 37.757196, -122.441681, NULL), (25, 101, 2225, '330', '2013-10-29 05:18:00', 37.757196, -122.441681, NULL), (26, 101, 2226, '330', '2013-10-29 05:19:00', 37.757196, -122.441681, NULL), (27, 101, 2227, '330', '2013-10-29 05:20:00', 37.757196, -122.441681, 'exit'); CREATE TABLE `billable_times` ( `id` int(11) NOT NULL AUTO_INCREMENT, `event_id` int(11) DEFAULT NULL, `device_number` varchar(255) DEFAULT NULL, `begin_time` datetime DEFAULT NULL, `end_time` datetime DEFAULT NULL, `duration` float DEFAULT NULL, PRIMARY KEY (`id`) ); </code></pre> <p>I'm using MySQL but any SQL flavor will be accepted. (I'll try to translate it to MySQL :).</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USGlenn
    1. USGlenn
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POAggregate dates from multiple rows into one
      1. USGlenn
      1. VTFavorite
    2. VO
      singulars
      1. POAggregate dates from multiple rows into one
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload