Fix R*Tree migration example in CHANGELOG.md

ocean · ocean · commit b793f51e08d5 · 2026-01-08T12:39:40.000+11:00
- Change table creation syntax from create table(:geo_regions, rtree: true)
  to create table(:geo_regions, options: [rtree: true]) to properly set
  table.options
- Remove explicit id column addition (Ecto creates it automatically)
- Normalize wording to 'multidimensional' for consistency
- Align with test patterns in test/rtree_test.exs and adapter's
  Keyword.get(table.options, :rtree, false) check
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -10,17 +10,16 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ### Added
 
 - **R*Tree Spatial Indexing Support**
-  - Full support for SQLite R*Tree virtual tables for multi-dimensional spatial indexing
-  - **Table creation**: Use `:rtree => true` option in Ecto migrations
+  - Full support for SQLite R*Tree virtual tables for multidimensional spatial indexing
+  - **Table creation**: Use `options: [rtree: true]` in Ecto migrations
   - **Dimensions supported**: 1D to 5D (3 to 11 columns total including ID)
   - **Column structure**: First column must be `id` (integer primary key), followed by min/max coordinate pairs
   - **Validation**: Automatic validation of column count (odd numbers only), first-column requirements (must be 'id'), dimensional constraints, and incompatible table options
   - **Table options**: R*Tree virtual tables reject standard table options (`:strict`, `:random_rowid`, `:without_rowid`) with clear error messages
   - **Use cases**: Geographic bounding boxes, collision detection, time-range queries, spatial indexing
   - **Migration example**:
     ```elixir
-    create table(:geo_regions, rtree: true) do
-      add :id, :integer, primary_key: true
+    create table(:geo_regions, options: [rtree: true]) do
       add :min_lat, :float
       add :max_lat, :float
       add :min_lng, :float
