Update documentation for AllowZeroDateTime.

Signed-off-by: Bradley Grainger <[email protected]>

Author: bgrainger

docs/content/connection-options.md

@@ -188,6 +188,13 @@ These are the other options that MySqlConnector supports. They are set to sensib
     <td>Allows user-defined variables (prefixed with <code>@</code>) to be used in SQL statements. The default value (<code>false</code>)
     only allows <code>@</code>-prefixed names to refer to command parameters.</td>
   </tr>
+  <tr>
+    <td>AllowZeroDateTime, Allow Zero DateTime</td>
+    <td>false</td>
+    <td>If set to <c>true</c> all `DATE`, `DATETIME` and `TIMESTAMP` columns are returned as `MySqlDateTime` objects instead of `DateTime`.
+    This allows the special “zero” date value `0000-00-00` to be retrieved from the database. If <code>false</code> (the default)
+    date columns are returned as `DateTime` values, and an exception is thrown for unrepresentable dates.</td>
+  </tr>
   <tr>
     <td>Compress, Use Compression, UseCompression</td>
     <td>false</td>

docs/content/tutorials/migrating-from-connector-net.md

@@ -127,3 +127,4 @@ The following bugs in Connector/NET are fixed by switching to MySqlConnector.
 * [#89159](https://bugs.mysql.com/bug.php?id=89159): `MySqlDataReader` cannot outlive `MySqlCommand`
 * [#89335](https://bugs.mysql.com/bug.php?id=89335): `MySqlCommandBuilder.DeriveParameters` fails for `JSON` type
 * [#91123](https://bugs.mysql.com/bug.php?id=91123): Database names are case-sensitive when calling a stored procedure
+* [#91199](https://bugs.mysql.com/bug.php?id=91199): Can't insert `MySqlDateTime` values