> 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-23.md).

# Legacy 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-23.md).
{% endhint %}

## Description

Tables nothing uses: unused tables (no code, and no rows or one test row), copies and scratch tables, and old tables that hold rows but that no code reads or writes.

## Tables

| Name                                                                                                                            | Columns | Comment                                                                                                                                                                                                                                                                                                                                                 | Type       |
| ------------------------------------------------------------------------------------------------------------------------------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- |
| [ai\_token\_budget](https://docs.snapfix.com/engineering-reference/db/tables/ai_token_budget.md)                                | 14      | Unused: zero rows, and no in-scope code refers to it. Meant for monthly Snapfix AI token and cost limits per site or user \[[ASK-182](https://github.com/snapfix/docs/blob/main/ASK.md#ask-182-what-monthly-snapfix-ai-budgets-apply-and-who-sets-them)].                                                                                               | BASE TABLE |
| [assetUserReg](https://docs.snapfix.com/engineering-reference/db/tables/assetuserreg.md)                                        | 20      | Unused: zero rows, and no in-scope code refers to it. Meant for one user's permissions on an old asset register (view all, create, delete, archive).                                                                                                                                                                                                    | BASE TABLE |
| [comply\_ContractorTag](https://docs.snapfix.com/engineering-reference/db/tables/comply_contractortag.md)                       | 12      | A tag on a contractor. Unused; only its model and migration refer to it.                                                                                                                                                                                                                                                                                | BASE TABLE |
| [comply\_SystemTag](https://docs.snapfix.com/engineering-reference/db/tables/comply_systemtag.md)                               | 12      | A tag on a compliance system. Unused; only its model and migration refer to it.                                                                                                                                                                                                                                                                         | BASE TABLE |
| [enum\_IntegrationSource](https://docs.snapfix.com/engineering-reference/db/tables/enum_integrationsource.md)                   | 10      | Legacy lookup of three PMS sources of room status changes (comtrol-lodginglink, oracle-opera and guestline, code in uuid); nothing reads it. tPri\_Log\_RoomStatusChange.uuid\_enum\_IntegrationSource holds the Pms enum values (comtrol, guestline, opera, hotsoft, cloudbeds and others) instead.                                                    | BASE TABLE |
| [flask\_test](https://docs.snapfix.com/engineering-reference/db/tables/flask_test.md)                                           | 9       | Unused. A leftover test table with one row on staging, and no in-scope code refers to it.                                                                                                                                                                                                                                                               | BASE TABLE |
| [guestline\_business\_job](https://docs.snapfix.com/engineering-reference/db/tables/guestline_business_job.md)                  | 14      | One task created for a Guestline group setup, linked to the Snapfix task (uuid\_tJob), with the Guestline room ID, a hash and log JSON. No in-scope code reads or writes it; about 1,800 rows, none added after December 2023 \[[ASK-242](https://github.com/snapfix/docs/blob/main/ASK.md#ask-242-can-the-unused-copy-and-scratch-tables-be-dropped)]. | BASE TABLE |
| [jira\_job](https://docs.snapfix.com/engineering-reference/db/tables/jira_job.md)                                               | 11      | Links a task (uuid\_tJob) to a Jira issue (jira\_ref), with the issue as JSON. No in-scope code reads or writes it, and no row is newer than 2022-01 \[[ASK-242](https://github.com/snapfix/docs/blob/main/ASK.md#ask-242-can-the-unused-copy-and-scratch-tables-be-dropped)].                                                                          | BASE TABLE |
| [package\_bundle\_server](https://docs.snapfix.com/engineering-reference/db/tables/package_bundle_server.md)                    | 14      | Links a server package to a marketing bundle, with an active flag and dates. Only a migration names it, and no row is newer than 2021-01 \[[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\_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\_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 |
| [schedule\_bug\_v2](https://docs.snapfix.com/engineering-reference/db/tables/schedule_bug_v2.md)                                | 19      | Copy of the schedule table (same columns), no row newer than 2021-10; 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 |
| [schedule\_debug\_log](https://docs.snapfix.com/engineering-reference/db/tables/schedule_debug_log.md)                          | 11      | Unused. A debug log of schedule events; no rows on staging and no in-scope code refers to it.                                                                                                                                                                                                                                                           | BASE TABLE |
| [schedule\_nfc02](https://docs.snapfix.com/engineering-reference/db/tables/schedule_nfc02.md)                                   | 19      | Copy of the schedule table (same columns), no row newer than 2021-10; only a migration names 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 |
| [std\_continents](https://docs.snapfix.com/engineering-reference/db/tables/std_continents.md)                                   | 2       | Reference list of continents, a two-letter code and an English name; only a seeder writes it and no code reads it.                                                                                                                                                                                                                                      | BASE TABLE |
| [std\_naics\_codes\_2](https://docs.snapfix.com/engineering-reference/db/tables/std_naics_codes_2.md)                           | 2       | One NAICS industry code at level 2, with its English title; only a seeder writes it and no code reads it (tPri\_Parent has a std\_naics\_codes column).                                                                                                                                                                                                 | BASE TABLE |
| [std\_naics\_codes\_3](https://docs.snapfix.com/engineering-reference/db/tables/std_naics_codes_3.md)                           | 3       | One NAICS industry code at level 3, with its English title; only a seeder writes it and no code reads it.                                                                                                                                                                                                                                               | BASE TABLE |
| [std\_naics\_codes\_4](https://docs.snapfix.com/engineering-reference/db/tables/std_naics_codes_4.md)                           | 3       | One NAICS industry code at level 4, with its English title; only a seeder writes it and no code reads it.                                                                                                                                                                                                                                               | BASE TABLE |
| [std\_naics\_codes\_5](https://docs.snapfix.com/engineering-reference/db/tables/std_naics_codes_5.md)                           | 3       | One NAICS industry code at level 5, with its English title; only a seeder writes it and no code reads it.                                                                                                                                                                                                                                               | BASE TABLE |
| [std\_naics\_codes\_6](https://docs.snapfix.com/engineering-reference/db/tables/std_naics_codes_6.md)                           | 3       | One NAICS industry code at level 6, with its English title; only a seeder writes it and no code reads it.                                                                                                                                                                                                                                               | BASE TABLE |
| [stripe\_product\_detail\_retired](https://docs.snapfix.com/engineering-reference/db/tables/stripe_product_detail_retired.md)   | 14      | Retired copy of Stripe product details, 4 rows, none newer than 2021-01; only a migration names 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\_AppVersion](https://docs.snapfix.com/engineering-reference/db/tables/tpri_appversion.md)                                 | 17      | Unused: an earlier list of app versions and server keys. Empty on staging and no in-scope code refers to it.                                                                                                                                                                                                                                            | BASE TABLE |
| [tPri\_Log\_Binary](https://docs.snapfix.com/engineering-reference/db/tables/tpri_log_binary.md)                                | 10      | Unused: an earlier log of files attached to tasks (URL and size). Empty on staging and no in-scope code refers to it.                                                                                                                                                                                                                                   | BASE TABLE |
| [tPri\_Log\_Job\_SoftFreeze](https://docs.snapfix.com/engineering-reference/db/tables/tpri_log_job_softfreeze.md)               | 7       | Unused: a log of tasks soft-frozen by a job. Empty on staging and no in-scope code refers to it \[[ASK-7](https://github.com/snapfix/docs/blob/main/ASK.md#ask-7-should-soft-freeze-still-run)].                                                                                                                                                        | BASE TABLE |
| [tPri\_MultiSiteChecklistTemplate](https://docs.snapfix.com/engineering-reference/db/tables/tpri_multisitechecklisttemplate.md) | 10      | Unused; empty, and no in-scope code names 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\_Parent\_copy\_2025-05-07](https://docs.snapfix.com/engineering-reference/db/tables/tpri_parent_copy_2025-05-07.md)       | 43      | A copy of tPri\_Parent taken on 2025-05-07; no in-scope code names 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\_UserHubspotContact](https://docs.snapfix.com/engineering-reference/db/tables/tpri_userhubspotcontact.md)                 | 18      | Unused; empty, and only its migration names it.                                                                                                                                                                                                                                                                                                         | BASE TABLE |
| [tPri\_UserParent\_copy1](https://docs.snapfix.com/engineering-reference/db/tables/tpri_userparent_copy1.md)                    | 20      | A copy of tPri\_UserParent; no in-scope code names it, and no row is newer than 2025-10 \[[ASK-242](https://github.com/snapfix/docs/blob/main/ASK.md#ask-242-can-the-unused-copy-and-scratch-tables-be-dropped)].                                                                                                                                       | BASE TABLE |
| [tPub\_ApiEndPoint\_v7\_LEGACY](https://docs.snapfix.com/engineering-reference/db/tables/tpub_apiendpoint_v7_legacy.md)         | 14      | An old copy of the v7 endpoint list; only its migration names it, and no row is newer than 2021-03 \[[ASK-242](https://github.com/snapfix/docs/blob/main/ASK.md#ask-242-can-the-unused-copy-and-scratch-tables-be-dropped)].                                                                                                                            | BASE TABLE |
| [tag](https://docs.snapfix.com/engineering-reference/db/tables/tag.md)                                                          | 20      | An image-analysis record (image URL and JSON per analysis type, as in tag\_vision). No in-scope code refers to it; staging holds one row \[[ASK-242](https://github.com/snapfix/docs/blob/main/ASK.md#ask-242-can-the-unused-copy-and-scratch-tables-be-dropped)].                                                                                      | BASE TABLE |
| [tag\_vision](https://docs.snapfix.com/engineering-reference/db/tables/tag_vision.md)                                           | 16      | Unused. Image-analysis results per image (image URL and JSON per analysis type); no rows on staging and 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 |
| [tag\_vision\_job](https://docs.snapfix.com/engineering-reference/db/tables/tag_vision_job.md)                                  | 10      | Unused. Links one image analysis (tag\_vision) to one task; no rows on staging and only its migration names 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 |
| [temp\_adrian\_todo\_data](https://docs.snapfix.com/engineering-reference/db/tables/temp_adrian_todo_data.md)                   | 4       | One-off export of task rows (account and group names, task title, checklist count); 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 |
| [temp\_adrian\_todo\_data2](https://docs.snapfix.com/engineering-reference/db/tables/temp_adrian_todo_data2.md)                 | 5       | One-off export of task rows (account name and type, group name, task title, checklist count); 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 |
| [temp\_adrian\_todo\_data3](https://docs.snapfix.com/engineering-reference/db/tables/temp_adrian_todo_data3.md)                 | 8       | A one-off scratch copy of task rows: account and group IDs and names, the task title and its checklist count. 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 |
| [temp\_adrian\_todo\_data4](https://docs.snapfix.com/engineering-reference/db/tables/temp_adrian_todo_data4.md)                 | 9       | A one-off scratch copy of task rows like temp\_adrian\_todo\_data3, with the task ID added. 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 |
| [temp\_adrian\_todo\_data5](https://docs.snapfix.com/engineering-reference/db/tables/temp_adrian_todo_data5.md)                 | 12      | A one-off scratch copy of task rows like temp\_adrian\_todo\_data4, with the planned flag, task type and origin added. 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 |
| [unittest](https://docs.snapfix.com/engineering-reference/db/tables/unittest.md)                                                | 10      | A leftover test table with one text, one JSON and one integer column; no in-scope code names 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 |
| [user\_blacklist](https://docs.snapfix.com/engineering-reference/db/tables/user_blacklist.md)                                   | 8       | A blocked username and mobile number; only its migration names it, and no row is newer than 2022-03 \[[ASK-242](https://github.com/snapfix/docs/blob/main/ASK.md#ask-242-can-the-unused-copy-and-scratch-tables-be-dropped)].                                                                                                                           | BASE TABLE |

## Relations

```mermaid
erDiagram

"std_naics_codes_3" }o--|| "std_naics_codes_2" : "FOREIGN KEY (naics_codes_2_code) REFERENCES std_naics_codes_2 (code)"
"std_naics_codes_4" }o--|| "std_naics_codes_3" : "FOREIGN KEY (naics_codes_3_code) REFERENCES std_naics_codes_3 (code)"
"std_naics_codes_5" }o--|| "std_naics_codes_4" : "FOREIGN KEY (naics_codes_4_code) REFERENCES std_naics_codes_4 (code)"
"std_naics_codes_6" }o--|| "std_naics_codes_5" : "FOREIGN KEY (naics_codes_5_code) REFERENCES std_naics_codes_5 (code)"

"ai_token_budget" {
}
"assetUserReg" {
}
"comply_ContractorTag" {
}
"comply_SystemTag" {
}
"enum_IntegrationSource" {
}
"flask_test" {
}
"guestline_business_job" {
}
"jira_job" {
}
"package_bundle_server" {
}
"qr_formdata_copy_20250513" {
}
"qr_formdata_copy_cg" {
}
"qr_formdata_ol1" {
}
"schedule_bug_v2" {
}
"schedule_debug_log" {
}
"schedule_nfc02" {
}
"std_continents" {
}
"std_naics_codes_2" {
  char_2_ code
}
"std_naics_codes_3" {
  char_3_ code
  char_2_ naics_codes_2_code
}
"std_naics_codes_4" {
  char_4_ code
  char_3_ naics_codes_3_code
}
"std_naics_codes_5" {
  char_5_ code
  char_4_ naics_codes_4_code
}
"std_naics_codes_6" {
  char_5_ naics_codes_5_code
}
"stripe_product_detail_retired" {
}
"tPri_AppVersion" {
}
"tPri_Log_Binary" {
}
"tPri_Log_Job_SoftFreeze" {
}
"tPri_MultiSiteChecklistTemplate" {
}
"tPri_Parent_copy_2025-05-07" {
}
"tPri_UserHubspotContact" {
}
"tPri_UserParent_copy1" {
}
"tPub_ApiEndPoint_v7_LEGACY" {
}
"tag" {
}
"tag_vision" {
}
"tag_vision_job" {
}
"temp_adrian_todo_data" {
}
"temp_adrian_todo_data2" {
}
"temp_adrian_todo_data3" {
}
"temp_adrian_todo_data4" {
}
"temp_adrian_todo_data5" {
}
"unittest" {
}
"user_blacklist" {
}
```

***

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