> For the complete documentation index, see [llms.txt](https://docs.ask.edvard.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ask.edvard.dev/database/ask-and-databases.md).

# Ask and Databases

How Ask handles database work.

Databases are easy to set up and easy to work with. Ask's design really shines when it comes to databases. Everything should be as simple and straightforward as possible. Ask reduces the needed boilerplate to get started to basically 0 lines, when compared to Flask.

## Practical

* All functions, variables, etc. used when working with databases are called on the built-in global `db` variable.

## Technical

* Ask uses **SQLAlchemy** behind the scenes. This can be useful to know when e.g. looking up errors.
* The default database for all Ask applications is **SQLite**, it is however possible to connect other databases, like e.g. MySQL.
* The database is by default stored in a file called *db.db* in your project's source directory.


---

# 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.ask.edvard.dev/database/ask-and-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.