Skip to content

Zio.Database (overview)

Where to Look

This bundle answers the question of where to look. Each entry point points to a different repository: Zio.code is the core code, Zio.node is the Neo4j ontology, Zio.entity is the PostgreSQL usr schema, and Zio.mongo contains collected data. Do not guess the repository by its name—you decide which one you refer to.

The same syntax works on both the .skills/ virtual sandbox and the local backend (FastAPI). The tool that holds the text does not see the repository, so handling of text is in a separate section (Zio.text).

They are not all the same. Do not assume that what works in one place will work elsewhere—this table is exhaustive.

Zio.code basic code Zio.node Neo4j ontology Zio.entity PostgreSQL usr Zio.mongo collection Zio.view virtual view
Create a container create_table() ✗ defined by the ontology create_table() ✗ ✗
Delete a container drop_table(force) ✗ defined by the ontology drop_table(force) ✗ ✗
Alter columns add_column() drop_column() rename_column() ✗ defined by the ontology ✗ ✗ ✗
Register create() create() merge() create() ✗ ✗
Update update() update() update() ✗ ✗
Delete delete() delete(detach) delete() ✗ ✗
Query fetch() count() info() fetch() aggregate() count() fetch() count() Read once fetch() info()
Lock on the table Yes — see basic code section None None ― ―

Zio.mongo is read‑only. It is a view of collected data, so writing is not possible. If you infer that something like Zio.mongo(...).create(...) would work by looking at the other sets, it does not.

Zio.node cannot create containers. Which nodes have which attributes is defined by the ontology, and humans manage it through the interface. Skills only insert values according to the ontology—if you want to set everything in one go, use Zio.ontology().

The meaning of force differs between the two. In Zio.entity, it means delete even if rows remain; in Zio.code, it means delete even if there are users of that table. Basic code expects rows to exist normally, so when you block by row, force becomes necessary and cannot serve as a blocker.

Open only the chapters you need. When everything was put into a single chapter, it became 40 KB, so even people who just wanted to see a basic code line had to go through the entire graph traversal. The names in the table above are the chapter titles.

  • Zio.code() — The basic code table that users manage on the screen. Locks applied to the table are explained here.
  • Zio.node() — Scans and aggregates the ontology graph.
  • Zio.entity() — Custom tables in the PostgreSQL usr schema.
  • Zio.mongo() — Collection for data ingestion. Read‑only.
  • Zio.view() — Runs virtual views created in DataStudio by name.
  • Browser JavaScript — The same SDK used in a browser.

(주)지오유 · 경기 용인시 처인구 유림로154번길(유방동 673-2) 20-13

CEO 신달수·Business no. 142-81-36612·E-commerce no. 용인처인-0118호·Privacy officer 신달수·Email shindalsoo@gmail.com·Tel 1833-3623·Fax 02-6918-4006