Databases
StackOverflow2013
Postsdbo
POMySQL GROUP BY DateTime +/- 3 seconds
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POMySQL GROUP BY DateTime +/- 3 seconds
    primarykey
    data
    text
    <p>Suppose I have a table with 3 columns:</p> <ul> <li>id (PK, int)</li> <li>timestamp (datetime)</li> <li>title (text)</li> </ul> <p>I have the following records:</p> <pre><code>1, 2010-01-01 15:00:00, Some Title 2, 2010-01-01 15:00:02, Some Title 3, 2010-01-02 15:00:00, Some Title </code></pre> <p>I need to do a GROUP BY records that are within 3 seconds of each other. For this table, rows 1 and 2 would be grouped together.</p> <p>There is a similar question here: <a href="https://stackoverflow.com/questions/4289345/mysql-datetime-group-by-15-mins">Mysql DateTime group by 15 mins</a></p> <p>I also found this: <a href="http://www.artfulsoftware.com/infotree/queries.php#106" rel="nofollow noreferrer">http://www.artfulsoftware.com/infotree/queries.php#106</a></p> <p>I don't know how to convert these methods into something that will work for seconds. The trouble with the method on the SO question is that it seems to me that it would only work for records falling within a bin of time that starts at a known point. For instance, if I were to get <code>FLOOR()</code> to work with seconds, at an interval of 5 seconds, a time of 15:00:04 would be grouped with 15:00:01, but not grouped with 15:00:06.</p> <p>Does this make sense? Please let me know if further clarification is needed.</p> <p><strong>EDIT:</strong> For the set of numbers, {1, 2, 3, 4, 5, 6, 7, 50, 51, 60}, it seems it might be best to group them {1, 2, 3, 4, 5, 6, 7}, {50, 51}, {60}, so that each grouping row depends on if the row is within 3 seconds of the previous. I know this changes things a bit, I'm sorry for being wishywashy on this.</p> <p>I am trying to fuzzy-match logs from different servers. Server #1 may log an item, "Item #1", and Server #2 will log that same item, "Item #1", within a few seconds of server #1. I need to do some aggregate functions on both log lines. Unfortunately, I only have title to go on, due to the nature of the server software.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USBrad
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTDuplicate
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POMySQL GROUP BY DateTime +/- 3 seconds
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POMySQL GROUP BY DateTime +/- 3 seconds
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POMySQL GROUP BY DateTime +/- 3 seconds
      1. This table or related slice is empty.
      1. VTUpMod
    1. COstill ambiguous. if the seconds were 1,2,3,4,5,6 then there are many groupings of 3 seconds possible where any given row could be in multiple groups...
      singulars
      1. POMySQL GROUP BY DateTime +/- 3 seconds
      1. USRandy
    2. CO@Randy, excellent point. Clarifying...
      singulars
      1. POMySQL GROUP BY DateTime +/- 3 seconds
      1. USBrad
    3. COThe reason that you need to pick distinct times is that otherwise grouping "within 3 seconds" probably doesn't make much sense. What if you had a series of 30 rows each exactly 2 seconds after the previous one? Now the first and last are almost a minute apart, but would be grouped because of the "chain" of rows.
      singulars
      1. POMySQL GROUP BY DateTime +/- 3 seconds
      1. USTom H
 

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