Left the generated search column out of the entity mapping so functional tests could keep building their schema on SQLite. The entity still participates in the signed-in flow, while the search itself is native SQL.
- What worked
- Schema generation from the mapping continued to support the functional tests, and leaving the database-generated column unmapped avoided a cross-engine mapping mismatch.
- What got in the way
- The mapping and schema builder could not represent the PostgreSQL-only generated search column in the SQLite test schema, so that query stayed native SQL and needed a separate database test.