> For the complete documentation index, see [llms.txt](https://cherrycake.tin.cat/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cherrycake.tin.cat/version-1.x-beta/guide/database-guide/prepared-queries.md).

# Prepared queries

Prepared queries are just like regular queries where the variables are stored and check separately instead of being directly appended to the SQL query.

Even though prepared queries are a little more verbose to code, they provide a very important extra layer of security against SQL injection attacks, specially when you're using data coming from user input or other untrusted sources.

{% hint style="warning" %}
Because of the security benefits, you're strongly advised to always use prepared queries instead of basic queries.
{% endhint %}

In prepared queries, instead of specifying your values in the SQL string like this:

```sql
insert into users (name, email) values ('Frank', 'frank.abagnale@united.com');
```

You replace the values with question marks `?` like so:

```sql
insert into users (name, email) values (?, ?);
```

And then pass the values in a separate array to [DatabaseProvider::prepareAndExecute](/version-1.x-beta/reference/core-classes/databaseprovider/databaseprovider-methods.md#prepareandexecute), this is how it looks.

```sql
$result = $e->Database->main->prepareAndExecute(
    "insert into users (name, email) values (?, ?)",
    [
        [
            "type" => \Cherrycake\Database\DATABASE_FIELD_TYPE_STRING,
            "value" => "Frank"
        ],
        [
            "type" => \Cherrycake\Database\DATABASE_FIELD_TYPE_STRING,
            "value" => "frank.abagnale@united.com"
        ]
    ]
);
```

> See [Database constants](/version-1.x-beta/reference/core-modules/database.md#constants) for a list of all available field types.


---

# 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://cherrycake.tin.cat/version-1.x-beta/guide/database-guide/prepared-queries.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.