> For the complete documentation index, see [llms.txt](https://docs.snapfix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snapfix.com/engineering-reference/db/tables/viewpoint-16.md).

# Qr tables

{% hint style="info" %}
Generated from the staging database schema, with descriptions drafted by agents ([how to read these docs](https://docs.snapfix.com/how-to-read.md)). [Source on GitHub](https://github.com/snapfix/docs/blob/main/spec/db/tables/viewpoint-16.md).
{% endhint %}

## Description

QR forms: the form codes, their submissions log, copies, and the log of QR requests sent by email.

## Tables

| Name                                                                                                                  | Columns | Comment                                                                                                                                                                                                  | Type       |
| --------------------------------------------------------------------------------------------------------------------- | ------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- |
| [qr\_formdata](https://docs.snapfix.com/engineering-reference/db/tables/qr_formdata.md)                               | 22      | One QR form of a group: the form fields (dynamic\_form\_json), the fixed task fields (hardcoded\_job\_json), app and poster texts and an expiry; a submission creates a task from it.                    | BASE TABLE |
| [qr\_formdata\_copy\_20250513](https://docs.snapfix.com/engineering-reference/db/tables/qr_formdata_copy_20250513.md) | 22      | Copy of qr\_formdata made on 2025-05-13; no in-scope code refers to it \[[ASK-242](https://github.com/snapfix/docs/blob/main/ASK.md#ask-242-can-the-unused-copy-and-scratch-tables-be-dropped)].         | BASE TABLE |
| [qr\_formdata\_copy\_cg](https://docs.snapfix.com/engineering-reference/db/tables/qr_formdata_copy_cg.md)             | 22      | Copy of qr\_formdata, no row newer than 2024-01; no in-scope code refers to it \[[ASK-242](https://github.com/snapfix/docs/blob/main/ASK.md#ask-242-can-the-unused-copy-and-scratch-tables-be-dropped)]. | BASE TABLE |
| [qr\_formdata\_log](https://docs.snapfix.com/engineering-reference/db/tables/qr_formdata_log.md)                      | 15      | One QR form submission, with the form, the task template, the submitted answers and the task it created. The submit throttle counts recent rows per form, and uuid\_qr\_formdata has no index.           | BASE TABLE |
| [qr\_formdata\_ol1](https://docs.snapfix.com/engineering-reference/db/tables/qr_formdata_ol1.md)                      | 22      | Copy of qr\_formdata, no row newer than 2024-01; no in-scope code refers to it \[[ASK-242](https://github.com/snapfix/docs/blob/main/ASK.md#ask-242-can-the-unused-copy-and-scratch-tables-be-dropped)]. | BASE TABLE |
| [tPri\_Log\_EmailQrRequests](https://docs.snapfix.com/engineering-reference/db/tables/tpri_log_emailqrrequests.md)    | 11      | One task request that came by email or from a QR code, with the request JSON, the file it produced and its start and end times; php-apis's email and QR task creation writes it.                         | BASE TABLE |

## Relations

```mermaid
erDiagram


"qr_formdata" {
}
"qr_formdata_copy_20250513" {
}
"qr_formdata_copy_cg" {
}
"qr_formdata_log" {
}
"qr_formdata_ol1" {
}
"tPri_Log_EmailQrRequests" {
}
```

***

> Generated by [tbls](https://github.com/k1LoW/tbls)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.snapfix.com/engineering-reference/db/tables/viewpoint-16.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
