Idea for UI/UX for timeslots

[hmpf]

We can use checkboxes (one per hour) in a table or css grid.

[hmpf]

This will mean it won't be possible to have shorter than one hour intervals of (not) sending notifications.

Proddata:

 count |  start   
-------+----------
     1 | 10:00:00
     1 | 15:00:00
     1 | 16:00:00
     1 | 09:00:00
     1 | 07:20:00
     3 | 07:00:00
     4 | 08:00:00
    93 | 00:00:00

 count |       end       
-------+-----------------
     1 | 08:00:00
     1 | 20:00:00
     1 | 14:30:00
     1 | 23:59:00
     2 | 22:00:00
     3 | 23:00:00
     4 | 16:00:00
    92 | 23:59:59.999999

[hmpf]

The end time == 14:30 is mine, as a test.

I will ask the owner of start time == 07:20 how important that level of precision is.

[hmpf]

Owner of the 0720 start time won't mind whole hours precision.

[hmpf]

While making the statistics I discovered that "end" is magic in postgres. (It is not possible to write SELECT end FROM argus_notificationprofile_timerecurrence;, you get a syntax error. SELECT start FROM argus_notificationprofile_timerecurrence; works fine.)

Maybe we should consider changing "end" to "endtime" and "start" to "starttime" in the database schema.

[hmpf]

This is probably why: https://www.postgresql.org/docs/current/sql-end.html