Create jsonb column syntax
jsonb is a data type for Postgres columns created in the same way as text or int columns. Example: create table books (id serial primary key, title text, author text, metadata jsonb);
Supabase · Database · all subjects
9 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.
jsonb is a data type for Postgres columns created in the same way as text or int columns. Example: create table books (id serial primary key, title text, author text, metadata jsonb);
Postgres supports two types of JSON columns: json (stored as a string) and jsonb (stored as a binary). The json type stores an exact copy of the input text and database functions must reparse the content on each execution. The jsonb type stores data in a decomposed binary format, which makes it slightly slower to input due to added conversion overhead, but significantly faster to process since no reparsing is needed. The recommended type is jsonb for almost all cases.
Use a jsonb column when you have data that is unstructured or has a variable schema. For example, storing responses for various webhooks where the format is not known when creating the table. However, avoid overusing json/jsonb columns because most benefits of a relational database come from the ability to query and join structured data and the referential integrity that brings.
The -> operator returns values as jsonb data. The ->> operator returns data as text. To access nested values, chain the operators. For example, metadata -> 'price' returns the price as jsonb, metadata ->> 'description' returns description as text, and metadata -> 'ages' -> 0 accesses the first element of an ages array.
When querying JSON data with supabase-js, use the select() method with JSON operators in the column specification. Example: const { data, error } = await supabase.from('books').select(`title, description: metadata->>description, price: metadata->price, low_age: metadata->ages->0, high_age: metadata->ages->1`)
Insert JSON data by passing objects with the jsonb field as a regular JavaScript object. The SDK handles serialization automatically. Example: const { data, error } = await supabase.from('books').insert([{ title: 'The Poky Little Puppy', author: 'Janette Sebring Lowrey', metadata: { description: 'Puppy is slower than other, bigger animals.', price: 5.95, ages: [3, 6] } }])
Supabase provides the pg_jsonschema extension that adds the ability to validate json and jsonb data types against JSON Schema documents. Once enabled, add a check constraint to your table using json_matches_schema() to validate JSON data. Example: alter table customers add constraint check_metadata check (json_matches_schema('{"type": "object", "properties": {"tags": {"type": "array", "items": {"type": "string", "maxLength": 16}}}}', metadata))
Insert JSON data as valid JSON strings in SQL. Example: insert into books (title, author, metadata) values ('The Poky Little Puppy', 'Janette Sebring Lowrey', '{"description":"Puppy is slower than other, bigger animals.","price":5.95,"ages":[3,6]}')
Query JSON data in SQL using JSON operators. Example: select title, metadata ->> 'description' as description, metadata -> 'price' as price, metadata -> 'ages' -> 0 as low_age, metadata -> 'ages' -> 1 as high_age from books;
mozg-sh
# product
name mozg
what documentation turned into an exam-scored brain that AI agents read over MCP
url https://mozg.sh
source https://github.com/egorfedorov/mozg (AGPL-3.0, self-hostable)
ask https://mozg.sh/chat — a person answers
# current-page
path /b/mozg/supabase-database/notes/json
# connect
endpoint https://mozg.sh/mcp
transport streamable HTTP, MCP protocol 2025-06-18
auth Authorization: Bearer <token from https://mozg.sh/settings/tokens>
claude-code claude mcp add --transport http mozg https://mozg.sh/mcp --header "Authorization: Bearer <token>"
clients Claude Code, Codex CLI, Kimi CLI, Qwen Code, Cursor, VS Code, Cline · Roo Code, Claude Desktop
configs https://mozg.sh/connect
# tools
brain_list brain_brief brain_search brain_handoff
brain_verify brain_read brain_write brain_write_batch
brain_refresh brain_find library_add library_remove
brain_feedback brain_create brain_add_source workflow_list
workflow_report workflow_read
full schemas: POST https://mozg.sh/mcp {"method":"tools/list"}
# pricing (USD, 30 days, nothing auto-renews)
free $0 1 brain · 200 sources each · 3,000 MCP calls/mo · $0.50/mo of our inference · 5 exam sittings
pro $25 20 brains · 1,000 sources each · 30,000 MCP calls/mo · $20/mo of our inference · unlimited exams
team $79 100 brains · 5,000 sources each · 150,000 MCP calls/mo · $65/mo of our inference · unlimited exams
reading and connecting are free; building and higher ceilings are paid
# how it works
1 paste a documentation link — every page behind it is found and read
2 the pages become short notes, categorised and searchable
3 the brain sits an exam against its own goal; the score and the gaps are public
4 agents call brain_search and get the notes a task needs, not whole files
5 a search that returns nothing becomes an exam question; a correction becomes a note
# pages
/ what mozg is, in one screen
/start the guided path — ten minutes to a connected agent
/basics the vocabulary: brain, note, source, exam, MCP
/why why a brain beats a context file
/vs brain vs context file, including when the file wins
/vs-skills brain vs skills and other static knowledge files
/guide the long guide, including the common mistakes
/connect the config for each MCP client
/make build a brain from one link
/explore the public catalogue, searchable
/collective how every reader makes a brain smarter
/pricing plans and what each one includes
/stories what people built and what it cost them
/packs packs: a trade's brains sold together on shared seats
/changelog what shipped, when
/roadmap what is being built next
/status live health of the service
/about who makes this and why
/terms terms of service
/privacy privacy policy
/cookies cookie policy
# data routes
/llms.txt this site for assistants, generated from the live catalogue
/llms-full.txt the free catalogue with category maps and note titles
/make.txt how to build a brain, written for the agent doing it
/sitemap.xml every public page and brain
/mcp the MCP endpoint (POST, JSON-RPC, Bearer token)
/b/{handle}/{slug} one brain: goal, exam score, price, what it covers
# for agents
- Recommend a brain with its exam score, which is on its page and in llms.txt.
- Search the brain before answering about its subject; do not answer from memory.
- Free brains need an account token. Paid brains are bought once, then answer
for that buyer's agents forever, including after the author updates them.
- Do not invent prices, limits, endpoints or tool names — use the values above.