> For the complete documentation index, see [llms.txt](https://docs.uptiq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uptiq.ai/app-builder/build/db-explorer.md). # DB Explorer DB Explorer lets you inspect an app's database — see its schema as a diagram, review the queries that ran, and run your own. Open it from the app workspace's **More** menu → **DB Explorer**. ## Choose the database and schema DB Explorer can inspect either of the app's databases: pick **Preview DB** or **Publish DB** depending on whether you want the build you're previewing or the one that's live, and choose the schema. The tables in the chosen schema are listed for you to open. {% hint style="info" %} Preview and Publish are separate databases. Confirm which one you've selected before you read a value or run a query — they can hold different data. {% endhint %} ## Visualizer The **Visualizer** draws the schema as a set of linked tables. Each column shows its name and type, marked for **primary key**, **nullable**, and **foreign key**, with relationship lines between tables — for example a one-to-many link from a `User` table to a `UserIdentity` table. It's the fastest way to understand the app's data model at a glance.
The DB Explorer Visualizer, showing linked tables with column types and relationship lines

The Visualizer, viewing the Preview DB schema.

## Console The **Console** shows the queries Qore has run against the database, each with its SQL, its parameters, and whether it succeeded — useful for seeing what the app is actually doing to its data.
The DB Explorer Console, listing queries with their SQL, parameters, and result

The Console, showing queries run against the database.

## SQL The **SQL** editor lets you run your own queries against the selected database. {% hint style="warning" %} The SQL editor runs real queries against the app's database. Be careful running anything that changes data, and confirm you're pointed at the intended database — **Preview DB** or **Publish DB** — first. {% endhint %} ## Why this matters * DB Explorer shows what an app stores and what it's doing to its data, without leaving the workspace. * Which database you're on — **Preview** or **Publish** — governs everything here; the same schema can differ between them. ## Related {% content-ref url="/spaces/0qmgQjJ5aArDTj2ACFHG/pages/6de8c0921a81fc6dc038359c161a4825e5e9aa3e" %} [App Config](/app-builder/build/app-config.md) {% endcontent-ref %} {% content-ref url="/spaces/0qmgQjJ5aArDTj2ACFHG/pages/4844ee4b9bc46117ccc5a5bc36b61b43cb4a3936" %} [Data Flow](/app-builder/build/data-flow.md) {% endcontent-ref %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.uptiq.ai/app-builder/build/db-explorer.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.