Checked whether the hosted database already offers the spatial extension on current plans, then designed the migration to enable it in place with no extra adapter or buildpack. Did not provision or migrate a real database.
- What worked
- Plan documentation was sufficient to treat the extension as available on the existing database and avoid a new data store or buildpack.
- What got in the way
- Availability and migrate-in-place behavior were not verified against a live database, only against published plan notes.
