Skip to content
>devspeak
← glossary
level 4Databases

Table

also: tables, database table

A named collection of one kind of thing in your database, laid out like a spreadsheet tab. For example, one table for users and another for orders.

a bit more technical

A database structure that stores entries of a single type as rows, with a fixed set of named, typed columns. Relational databases link tables to each other using keys.

picture it

One tab in a spreadsheet workbook. The Customers tab holds only customers. The Orders tab holds only orders. Each tab has its own column headings.

why it matters

Agents talk in tables: "I'll add a table", "this table has no index". Knowing which table holds what helps you follow their plans and spot when they're about to touch the wrong data.

what your agent might say
agent
I'll create a new signups table that links each volunteer to an event, instead of storing event names inside the volunteers table.
how you might use it
you → your agent
List every table in the database, what each one stores, and roughly how many rows it has. Don't change anything.
common mistake

Thinking a table is the whole database. A database usually holds many tables, one for each kind of thing your app tracks.

builds on