Table
One list in the database holding one kind of thing, like customers or orders, laid out in rows and columns.
What it is
A table is like a spreadsheet tab: each row is one item (one customer) and each column is one piece of information about it (name, email). A database usually has several tables.
Thinking in tables is the fastest way to describe an app's data: "a Projects table and a Tasks table; each task belongs to a project." Builders sometimes call them models, collections, or entities.
Don't confuse a database table with a table on screen. The screen might show a table, a list, or cards from the same data.
How to ask for it
“We need to save projects and the tasks in them.”
“Create two tables: Projects (name, owner, due date, status) and Tasks (title, assignee, done, project). Each task belongs to exactly one project, and a project can have many tasks.”
Naming the tables, their columns, and how they connect gives the builder the data model instead of making them guess one.
You've seen this in
- AAn Airtable base
- AA Shopify product list
- TThe rows behind any admin panel