> For the complete documentation index, see [llms.txt](https://docs.tomorrowx.com/cap/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tomorrowx.com/cap/product-reference/concepts-and-terminology/databases.md).

# Databases

Databases are another fundamental concept of <code class="expression">space.vars.X\_Product\_Name</code>. In <code class="expression">space.vars.X\_Product\_Name</code> terminology, a database is anything that can be connected to via a JDBC driver.

JDBC drivers are connectivity modules for the Java language.

The term **database** refers to a system that is capable of storing data in a structured relational manner.

Alongside databases, there are a couple of terms that are important, which are listed below *(Tables through Keys)*.

## Tables

Tables are the name of the individual file within the database where a given set of data is stored. Sample table names are **CUSTOMERS** and **ACCOUNTS**. Some <code class="expression">space.vars.X\_Product\_Name</code> rules have the ability to create tables or `read/write` data to them.

## Schema

A schema is a way to segment a database into multiple entities i.e. there can be two schemas on the same database containing the same table names. For example, there can be a **PRODUCTION** schema that contains an **ACCOUNTS** table as well as a **TEST** schema that contains an **ACCOUNTS** table.

## Rows and columns

Rows and columns refer to the individual elements inside a table. For example, like a spreadsheet where all of the columns have a name.

## Keys

Typically, all tables have keys that map to one or more columns in the table. In most cases tables have unique keys, which is enforced at the database level.


---

# 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.tomorrowx.com/cap/product-reference/concepts-and-terminology/databases.md?ask=<question>&goal=<endgoal>
```

`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.