Multi-model writes

← All examples

Write a row, its embeddings and searchable text with the same record ID. Each write call commits separately. Reconnect search results to their source row in the application and reconcile uncertain writes before retrying.

1. 01
   Save the source rowKeep the original fields under a stable record ID.
2. 02
   Write search entriesUse that ID for the embedding and text index.
3. 03
   Find a matching IDChoose the search method your question needs.
4. 04
   Read the originalFetch the source row to show its current details.

Use shared IDs across query modelsCopy Anchor Link

• Search and connect product records — Store a product row, embedding and searchable text under the same ID.
• Find an article by words or meaning — Store an article row, embedding and searchable body.
• Connect profiles and search bios — Store a profile with its follows relationship, then index the bio by meaning.
• Filter events and search their text — Store structured event fields and index the event text separately.
• Store and retrieve an agent’s notes — Connect a note’s fields, embedding and searchable text through a shared ID.

Keep writes consistentCopy Anchor Link

Track each response. If a write times out, check its outcome before replaying it. A new SDK call may use a new key, and a key alone does not guarantee SQL replay safety. See idempotency.