To reproduce

This test fails:

@Test
public void test12HourClockAfterMidnight() throws Exception {
  DateFormat fmt = compiler.compile("MM/dd/yyyy HH:mm:ss a", false);
  long millis = fmt.parse("04/07/2018 12:30:00 AM", defaultLocale);
}

QuestDB expects hours in timestamps in the 12-hour clock system to be between 00 - 11
.
It interprets 00:01 AM as one minute after midnight. However, the usual way to format 1 minute after midnight is 12:01 AM and not 00:01 AM. The 12-hour clock transitions from 12:59 AM to 01:00 AM. 🤯

It sounds counter-intuitive, the transition 1 hour after midnight looks abrupt. but it makes sense if you think about good ol' analog clock. See: https://en.wikipedia.org/wiki/12-hour_clock

A fix should change:

1. both the generic DateFormat parser and the specialized compiler
2. also the reverse part: timestamp printing

QuestDB version:

7.4.2

OS, in case of Docker specify Docker and the Host OS:

irrelevant

File System, in case of Docker specify Host File System:

irrelevant

Full Name:

Jaromir Hamala

Affiliation:

QuestDB

Have you followed Linux, MacOs kernel configuration steps to increase Maximum open files and Maximum virtual memory areas limit?

• Yes, I have

Additional context

No response