Complete technical documentation of the IndexedDB database structure and relationships
The database uses IndexedDB with a three-store structure to manage tables, columns, and data records. This design provides flexibility while maintaining data integrity through relationships.
| Field | Type | Description |
|---|---|---|
| id | auto | Unique identifier |
| name | string | Table name |
| created | date | Creation timestamp |
| modified | date | Last modified timestamp |
| Field | Type | Description |
|---|---|---|
| id | auto | Unique identifier |
| tableId | foreign key | References Tables.id |
| name | string | Column name |
| type | string | Data type (text, number, etc.) |
| order | number | Display order |
| options | json | Column-specific settings |
| Field | Type | Description |
|---|---|---|
| id | auto | Unique identifier |
| tableId | foreign key | References Tables.id |
| data | json | Record data object |
| created | date | Creation timestamp |
| modified | date | Last modified timestamp |
The database uses a one-to-many relationship structure:
The schema is implemented using IndexedDB object stores: