9 min readUpdated September 22, 2026
How databases work in AI-built apps
Tables, rows, relationships, queries and access rules — what your AI tool created for you, and how to read it without learning SQL first.
Databases
A database stores records that an app reads and changes through queries. Learn how tables, filters and access rules affect the rows a user can see.
Where should I start with databases?
Start with the guide that matches your question or the error you can see. Each guide below names the problem, gives checks you can run, and links to related reading.
Why can saved data disappear from a list?
Illustrative case: Account A owns a draft, but its list requests only published records. The draft can be stored correctly and still be absent because the query filter excludes it. An access policy can independently exclude rows, so inspect both the application query and the database's access decision.
record 1: owner=A, status=draft
record 2: owner=B, status=published
A requests: own records with status=published
Expected result: []The empty result above does not justify returning Account B's record. Change the status filter only if the screen is meant to show drafts; preserve the ownership restriction. Administrator tooling seeing both records does not establish what an ordinary user should receive.
What does a persistence check include?
- 1Create a record using an isolated test account and confirm the server accepts it.
- 2Reload and retrieve that same record through the app's normal read path.
- 3Edit one field, refresh again and confirm the stored value rather than the temporary screen value.
- 4Verify another account cannot read or edit it by changing the record identifier.
Use the database guide to understand tables and queries. Follow the linked row-security and frontend-access guides when permissions or empty results are the problem. Do not repair a missing row by turning off security.
Read the databases guides
Looking for something else? Browse every topic.