title: Bug on MySQL side with timestamps?
body: <p>I think I found a bug on MySQL side.
  To reproduce : Just create a table with one column being a timestamp type :</p>
  <pre><code>create table test
  (
      time timestamp null
  );
  </code></pre>
  <p>Now insert a row with exact date : '2022-03-27 02:00:00':</p>
  <pre><code>insert into test value ('2022-03-27 02:00:00');
  </code></pre>
  <p>I have error :</p>
  <pre><code>Data truncation: Incorrect datetime value: '2022-03-27 02:00:00' for column 'time' at row 1
  </code></pre>
  <p>Looks like it happens only with date from 2022-03-27 02:00:00 to 2022-03-27 03:00:00 not included.</p>
  <p>Could anyone reproduce that and confirm that's a bug from MySQL side ? Or did I miss something here ? Using MySQL 8.0.30 (issue happens with MySQL workbench and CLI so it's not some formatting that would happen before MySQL from any software) </p>
  <p>Edit : I have the same error when I try adding the real associated timestamp itself :</p>
  <pre><code>Incorrect datetime value: '1648346400' for column 'time' at row 1
  </code></pre>