Tavlon Is Not a Database
Tavlon is not intended to replace a database. Databases are designed for storing, querying, indexing, securing, and managing application data. Tavlon has a different purpose: defining reusable table structures in readable text.
Tavlon focuses on the table definition itself. It helps describe what a table is, how its columns are structured, which fields are required or optional, and how the structure can be reused across outputs.
What Databases Are Good At
Storing large amounts of application data
Querying and filtering data efficiently
Managing relationships between records
Supporting transactions and concurrency
Providing indexes, permissions, and long-term data management
Tavlon does not try to duplicate those database responsibilities. Instead, Tavlon helps define table structure in a way that remains readable, versionable, and reusable.
What Tavlon Is Designed For
Defining table structures in readable text
Creating a single source of truth for table layout
Versioning and auditing table definition changes
Rendering table definitions visually
Exporting table structures to Word, Excel, PDF, NX, AutoCAD, and requested formats
Table Definition Instead of Database Schema
A database schema describes how data is stored and managed inside a database. A Tavlon table definition describes the user-facing structure of a table so that it can be rendered, reviewed, reused, and exported.
Locations: {
header: {
STRING Name *Required,
STRING Address *Optional,
Array Shifts (
STRING ShiftName,
TIME StartTime,
TIME EndTime
)
}
}This definition describes a reusable table structure. It is not a database table creation script. It is a Tavlon definition that can be interpreted by Tavlon and reused across outputs.
Database vs Tavlon
| Question | Database | Tavlon |
|---|---|---|
| Primary purpose | Store and query application data | Define reusable table structure |
| Starting point | Database schema | Readable TDL text |
| Main concern | Persistence, queries, indexes, transactions | Structure, reuse, versioning, export |
| Typical users | Developers, DBAs, applications | Users defining reusable tables and outputs |
| Output role | Data source for applications | Source definition for rendered and exported tables |
Tavlon can work alongside databases, but it serves a different role. A database manages data. Tavlon defines reusable table structure for rendering, review, versioning, and export.