Database

Menu: Database group in the left sidebar (must be enabled in Edit Menu)
Route prefix: /_Admin/database/...?SiteId={siteGuid}

The Database group manages multiple data stores within a site: IndexedDB dynamic tables, table relations, key-value storage, and browsing and data maintenance for external SQLite / MySQL / SQL Server tables. SQL Logs shows SQL records produced by scripts and the admin backend. Scripts access these stores uniformly through k.DB (for SQLite see k.DB.sqlite).

Difference from Content

	Database	Content → Content
Model	Custom table schemas, KV, external DB tables	Content types + content folders
Typical use	Business tables, cache keys, integrating existing SQL databases	CMS entries bindable to pages
API	k.DB	k.content

The two can be used together; do not treat them as one modeling system.

Advanced menu

The Database group and its sub-items are marked advanced in Edit Menu. If they are not checked, this group does not appear in the left sidebar.

How to Open

1. In Edit Menu, check Database and the sub-items you need.
2. Expand Database in the left sidebar.

Submenus (same order as the admin)

Menu	Route	Permission (feature)	Doc
IndexedDB Tables	/database/table	database	IndexedDB tables (this section)
IndexedDB Table Relations	/database/table-relation	tableRelation	Table relations
Key-Value Storage	/database/key-value	keyValue	Key-value storage
SQLite Tables	/database/sqlite-table	database	SQLite tables
MySQL Tables	/database/mysql-table	database	MySQL tables
SQL Server Tables	/database/sqlserver-table	database	SQL Server tables
SQL Logs	/database/sql-logs	database·log	SQL logs

Development reference (KScript API)

Menu	API doc
IndexedDB tables	k.DB.indexedDb
SQLite / MySQL / SQL Server tables	k.DB · k.DB.sqlite
Key-value storage	k.DB (KV APIs; see child doc)
SQL logs	Read-only observation; no dedicated k.* CRUD

Edit routes without sidebar menu items

The following pages are opened from table lists. Breadcrumbs still belong to the corresponding table-type menu (dbType query parameter highlights IndexedDB / SQLite / MySQL / SQL Server):

Route	Description
/database/table/columns	Edit table columns (column definitions)
/database/table/data	Browse and filter table data
/database/table/edit-data	Create or edit a single row

Deep-link examples:

/_Admin/database/table/columns?SiteId={siteGuid}&id={tableId}&dbType=IndexedDb
/_Admin/database/table/data?SiteId={siteGuid}&id={tableId}&dbType=Sqlite

dbType values match the admin (e.g. IndexedDb, Sqlite, Mysql, SqlServer); confirm in the address bar.

Suggested reading order

If you are modeling site data from scratch, a common order is:

1. IndexedDB tables — default dynamic tables within the site
2. Table relations — multi-table associations (requires existing IndexedDB tables)
3. Key-value storage — simple KV
4. SQLite / MySQL / SQL Server — read as needed depending on external database integration
5. SQL logs — troubleshooting and auditing

Related

Doc	Description
Site admin menu overview	Full menu tree
Development	Calling k.DB from Code
k.DB	Script API
k.DB.sqlite	SQLite queries and table operations