AutessaDB
Tables and data modeling
AutessaDB tables are typed, related and computed: text, number, select and media columns, foreign keys, AutessaScript computed columns, write-once ledger tables and one-click knowledge bases.
-- why it matters
What does tables and data modeling cover?
How AutessaDB models data: typed tables, foreign keys and joins, computed columns, append-only tables and knowledge bases for document search.
A database is only as useful as its shape. AutessaDB gives you typed columns that people, scripts and agents all respect, links between tables, values that compute themselves, tables that can never be rewritten, and a one-click preset for documents.
Who works here
Builders and data owners design tables; teammates add and edit rows in the grid; agents and scripts read and write the same tables through tools and the API.
In one sentence each
- Tables and column types · AutessaDB tables have typed columns from Short Text to Audio, with required flags, value limits, select lists and system columns on every row.
- Foreign keys and joins · Integer columns can be foreign keys to rows in another table, and join queries follow them with filters, while each joined table keeps its own security.
- Computed columns · A computed column runs a short script over the row after each write and stores the answer, recomputing only when the columns it depends on change.
- Append-only tables · Append-only tables are write-once: rows can be added and read but never changed or removed, and the setting can be turned on but never off.
- Knowledge bases · Drag files or whole folders into a knowledge base and they are indexed for semantic search, with a Create Agent shortcut for a ready-made search agent.
-- subtopics
Everything in tables and data modeling
Tables and column types
AutessaDB tables have typed columns from Short Text to Audio, with required flags, value limits, select lists and system columns on every row.
Read more →Foreign keys and joins
Integer columns can be foreign keys to rows in another table, and join queries follow them with filters, while each joined table keeps its own security.
Read more →Computed columns
A computed column runs a short script over the row after each write and stores the answer, recomputing only when the columns it depends on change.
Read more →Append-only tables
Append-only tables are write-once: rows can be added and read but never changed or removed, and the setting can be turned on but never off.
Read more →Knowledge bases
Drag files or whole folders into a knowledge base and they are indexed for semantic search, with a Create Agent shortcut for a ready-made search agent.
Read more →-- on screen
What it looks like
Foreign keys and joins
Computed columns
-- faq
Questions about tables and data modeling
What column types does AutessaDB support?
Short Text, Long Text, File, Image, Video, Audio, Integer, Decimal, Boolean, Single Select and Multi Select. Every table also has system columns for id, creation time and last update.
Does AutessaDB support foreign keys?
Yes. An Integer column can be a foreign key to a row in another table, and those columns are always indexed.
What language are computed columns written in?
AutessaScript, the same JavaScript-based language Autessa uses for script tools, with a slimmer context focused on the row.
Can I turn append-only off?
No. Append-only is a one-way latch. You can turn it on for an existing table, but never off, which is what makes it trustworthy.
Is a knowledge base a separate vector database?
No. It is an AutessaDB table pre-configured for document storage and semantic search, so it shares the same security, sharing, triggers and APIs as every other table.
Other areas of AutessaDB
100% customizable, code and all
Make AutessaDB fully your own.
Use it out of the box, then change anything. Ask Autobot, Autessa’s AI builder, for a new field, screen, report, workflow or agent and it builds it into your copy of the app. Or open the code and edit it yourself. Nothing is locked: the app, its data and its code are yours.
Start free and make it yours