Add documentation: Document Database Schema #6
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Document Database Schema
Description
This document provides comprehensive information about the database schema, including table structures, data types, relationships, and constraints. It focuses on the core tables related to document storage and management, as well as the storage schema. This documentation is crucial for developers and database administrators to understand how data is stored and related within the application, facilitating data modeling, querying, and maintenance of data integrity.
Target Audience
Database Schema
This section details the structure of the key tables within the database.
Data Models
1.
documentsTableThis table stores metadata about individual documents.
document_sections(one-to-many),documents_with_storage_path(one-to-one).| Column Name | Data Type | Constraint