Please add a server option that users can set to On or OFF, which if it is ON, will allow 24:00 as a valid Time. Per the discussion and sample use case given here:
there is now no way to represent the terminus of the 24-hour clock unambiguously . The Time datatype is supposed to be based on the 24-hour day, but we can only represent the beginning of the 24-hour day with 00:00. We cannot represent the end-point.
The Time datatype has nothing to do with calendrical time; as far as the Time datatype is concerned, time consists of an eternal 24-hour day. There is no concept of yesterday or tomorrow in the Time datatype. When mapping data with Time, we should not be concerned with tomorrow or yesterday. If we are concerned with tomorrow or yesterday, or a particular day in the calendar, we use DateTime.
So a retort that "24:00" belongs to the NEXT day is not a valid objection as the retort is conflating DateTime with Time. To repeat, there is no concept of NEXT DAY as far as the Time datatype is concerned. 24:00 is NOT "tomorrow". It is the terminus of TODAY.