DOC Document fixed DBField options array

Author: GuySartorelli

en/02_Developer_Guides/00_Model/04_Data_Types_and_Casting.md

@@ -81,10 +81,13 @@ to be applied to all existing and new records when the column is added in the da
 for the first time. You do this by passing an argument for the default value in your
 `$db` items.
 
-For integer values, the default is the first parameter in the field specification.
+For integer and floating point values, the default is the first parameter in the field specification.
 For string values, you will need to declare this default using the options array.
 For enum values, it's the second parameter.
 
+> [!WARNING]
+> MySQL doesn't support default values for `TEXT` columns, so you should not try to set a default value using the options array for `Text` or `HTMLText` fields when using MySQL.
+
 For example:
 
 ```php
@@ -98,7 +101,8 @@ class Car extends DataObject
     private static $db = [
         'Wheels' => 'Int(4)',
         'Condition' => 'Enum("New,Fair,Junk", "Fair")',
-        'Make' => 'Varchar(["default" => "Honda"])',
+        // For Varchar, the size must be passed before the options array.
+        'Make' => 'Varchar(255, ["default" => "Honda"])',
     ];
 }
 ```

en/08_Changelogs/6.2.0.md

@@ -119,3 +119,9 @@ It's best practice to avoid using deprecated code where possible, but sometimes
 ## Bug fixes
 
 This release includes a number of bug fixes to improve a broad range of areas. Check the change logs for full details of these fixes split by module. Thank you to the community members that helped contribute these fixes as part of the release!
+
+### `DBField` options array
+
+Some [`DBField`](api:SilverStripe\ORM\FieldType\DBField) implementations take an array of options in the constructor. This is notably used to set default values for [`DBString`](api:SilverStripe\ORM\FieldType\DBString) subclasses as documented in the [default values documentation](/developer_guides/model/data_types_and_casting/#default-values) but can be used for other purposes as well.
+
+When creating columns in the database, the options array wasn't being correctly passed through to the constructor, which made setting default values for string columns impossible among other things. This has been fixed.