# Table (/catalog/table)

A table you keep by hand, such as a budget, a reading log or a list of contacts, with the columns you choose.

Identifier: `core.table`



## Fields [#fields]

| Field | Kind | Description |
| - | - | - |
| `title` | `string`, required | The name of the table. |
| `description` | `string` | What the table is for. |
| `columns` | `object`, required | The table's columns, by name. A column has a `type` and may have a `label`, `description`, `required`, `enum_values`, `format`, `max_length`, `minimum`, `maximum`, `type_constraints`, `adds_up` and `searchable`, as a column a type declares does. |

## Settings [#settings]

| Setting | Value |
| - | - |
| `plural` | Tables |
| [`title_field`](/catalog/type-rules#display-hints) | `title` |
| [`body_field`](/catalog/type-rules#display-hints) | `description` |
| [`icon`](/catalog/type-rules#display-hints) | `lucide:table` |
| [`merge_policy`](/catalog/type-rules#merge-policy) | `last_writer_wins` for every field |

The item holds one table, named `table`, whose columns are its `columns` property, keyed by column name. [Field kinds](/catalog/field-kinds#columns) lists the keys a column takes. Its rows are written to `table` with [`writeTableRows`](/reference/api/tables/writeTableRows) or `marfa rows`, as [Tables](/build/tables) explains.

## Example [#example]

```json
{
  "type": "core.table",
  "properties": {
    "title": "Trip budget",
    "description": "What the Lisbon trip costs, by day.",
    "columns": {
      "day": { "type": "date", "label": "Day", "required": true },
      "item": { "type": "string", "label": "What", "searchable": true },
      "category": { "type": "enum", "label": "Category", "enum_values": ["travel", "food", "stay"] },
      "amount": { "type": "number", "label": "Amount", "minimum": 0, "adds_up": "sum" }
    }
  }
}
```
