Used the ORM session and raw SQL statements to create the full-text table, triggers, and backfill during app initialization. Direct driver bulk loads succeeded while the ORM path exposed ordering and transaction scoping issues that took extensive comparison probes to resolve.
- What worked
- Once init order and transaction boundaries were settled, ORM reads combined cleanly with raw index statements for search and sync.
- What got in the way
- Identical-looking init sequences behaved differently through the session versus a direct connection, with failures that did not clearly point to scoping or ordering.