> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# What Is a Relational Database and Why Does It Matter?
- URL: https://blog.jestor.com/what-is-a-relational-database-operations/
- Published: 2026-09-17T22:32:39.000Z
- Updated: 2026-09-17T22:32:39.000Z
- Author: Bruno Bannach

A **relational database** stores each piece of information once and connects records to each other rather than copying values between them. In operations, that is the difference between data that stays consistent and data that drifts.

## What copying costs you

Duplication rarely announces itself as a problem. It appears as inconsistencies nobody can explain.

- The same client with three slightly different names
- A price updated in one place and not the other
- Reports that disagree depending on their source
- Hours spent reconciling records that should be identical

## Relationship types

- **One-to-many** — each child has exactly one parent, like a payment and its supplier
- **Many-to-many** — records connect freely in both directions, like an expense split across cost centres
- **Connected fields** — display data from the linked record rather than storing a copy
- **Label fields** — determine what is shown when selecting a related record

## How it works in Jestor

1. Create a table in **Jestor** for each core entity — clients, products, suppliers, cost centres.
2. Connect them with relationship fields instead of copying values.
3. Choose one-to-many for hierarchical relationships, many-to-many for shared ones.
4. Set the label field on each related table so selection shows names, not identifiers.
5. Build formulas and conditional fields that read across the relationships.

## Why choose Jestor for relational operations?

In **Jestor**, tables are a relational database at the centre of the operation rather than a storage layer behind an interface — which is what makes automation, scale, and consistent reporting possible.

A card can surface data from several linked tables at once, including a parent's parent, so context is available without navigation.

## Frequently Asked Questions

### What is a connected field?

A field that displays data from a linked record rather than storing a copy. See [jestor.com](https://jestor.com/?ref=blog.jestor.com).

### When do I need many-to-many?

When a record legitimately belongs to more than one other, like a shared expense.

### Can formulas read across tables?

Yes, formulas and conditional fields work over relationships.

## Video Tutorial: Step by Step

Check out other practical tutorials on the Jestor YouTube channel.

## Get to know Jestor

With **Jestor**, you can automate workflows, connect teams, and build internal systems your way — all without code and powered by **AI**. Discover Jestor at [jestor.com](https://jestor.com/?ref=blog.jestor.com) and see how to take your company's operations to a new level of efficiency and control.