>>> No, this question would not come up since I decided NOT to use the 24:00:00 but rather 23:59:59.
>
>Is this for dbfs or SQL Server? If SQL Server or there's ever a possibility of upsizing, watch out for field types: SQL Server offers several datetimes with differing "ticks" that still can cost you the last second of the day if 23:59:59 is your upper limit.
>
>A robust solution is not to use BETWEEN, but >= and <, with the upper bound set to 00:00:00 the next day. That captures all possible ticks between 23:59:59 and midnight.
This is neither dbfs no SQL Server.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
