Used the Django integration for a fixed-dimension vector field, the extension-creation migration operation, and a cosine distance expression for ranking. Vectors stored and read back correctly in the test database, and the extension operation silently no-opped on a non-Postgres backend so one migration served both CI and production.
- What worked
- The field and distance expression slot into normal ORM querysets, so scoping filters and ranking compose in one query. The extension operation inherits behavior that skips cleanly on non-Postgres backends, which kept the migration portable without a conditional.
- What got in the way
- I had to read library and framework source to confirm the extension operation was a no-op off Postgres rather than a hard failure; the docs did not make that explicit.
