> For the complete documentation index, see [llms.txt](https://uci.sunbird.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://uci.sunbird.org/use/developer/database-schema/database-formsdb.md). # Postgres Forms Database ### Introduction This database is built on PostgreSQL and manages all ODK questions and answers, as well as their respective states. It tracks the questions posed to users and the anticipated follow-up inquiries. ### 1. Table Schema * Table Name - question | Column Name | Type | Description | | -------------- | --------- | ------------------------------------------------------------------------ | | id | UUID | Unique identifier for the record. | | form\_id | Varchar | This is odk formid, while we create odk form we added in the xml. | | form\_version | Varchar | This is odk form version, while we create odk form we added in the xml. | | x\_path | Varchar | This is path of question get from odk form. | | question\_type | Varchar | Type of the question like String, Single Select and Multi-Select. | | meta | Jsonb | JSON data structure its contain the question which we sent to our users. | | updated | Timestamp | Timestamp indicating when the record was last updated. | | created | Timestamp | Timestamp indicating when the record was created. | | --- | | | ### 2. Table Schema * Table Name - xmessage | Column Name | Type | Description | | ----------------- | ------- | ------------------------------------------------------------------------------- | | id | Long | Unique identifier for the record. | | phone\_no | Varchar | Phone number associated with the user. | | message | Varchar | The content of the message which we sent to user. | | is\_last\_message | Boolean | A boolean flag indicating if this is the last response in a series of messages. | | --- | | | ### 3. Table Schema * Table Name - xmessage\_state | Column Name | Type | Description | | --------------- | ------- | ----------------------------------------------------------- | | id | Long | Unique identifier for the record. | | phoneNo | Varchar | Phone number associated with the user. | | state | Text | XML data for previous question. | | previous\_path | Varchar | Path or location of the previous question. | | bot\_form\_name | Varchar | Name or identifier of the bot form associated with the bot. | | --- | | | --- # 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://uci.sunbird.org/use/developer/database-schema/database-formsdb.md?ask=&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.