@ Mantian de Guang: after a whole day, you just want to get it done in one sentence, right? Basically, it doesn't make sense. If you don't get stuck with an SQL statement, I believe you will soon be able to write code. If the requirement is unclear, the interval is less than 1 minute, or the standard minute isolation is used. (08:57:59 and 08:58:03 are counted as two minutes.) When you make it clear, then
@ Mantian de Guang: after a whole day, you just want to get it done in one sentence, right? Basically, it doesn't make sense. If you don't get stuck with an SQL statement, I believe you will soon be able to write code. If the requirement is unclear, the interval is less than 1 minute, or the standard minute isolation is used. (08:57:59 and 08:58:03 are counted as two minutes.) When you make it clear, then
@ Mantian de Guang: after a whole day, you just want to get it done in one sentence, right?
Basically, it doesn't make sense. If you don't get stuck with an SQL statement, I believe you will soon be able to write code.
If the requirement is unclear, the interval is less than 1 minute, or the standard minute isolation is used. (08:57:59 and 08:58:03 are counted as two minutes) This is when you make it clear, and the sample is not described in the example. How can we process such data?
08:57:59
08:58:03
08:58:12
08:59:02
08:59:50
If it is not more than 1 minute apart, it will continue to be taken until more than 1 minute has elapsed. (Will this description be more accurate, or will it be more difficult to misunderstand ?)
In this case, you can add a field and put the code processing result in the field. Then you can group.
The importance of using an SQL statement or multiple SQL statements is not that strong.
I am opposed to performance-only theory.