Database
Stores
truth
truth
Databases 101
Databases in Wappler, from zero to query: connections, choosing drivers, and turning tables into usable data.
Why databases exist
Section titled “Why databases exist”A database is usually made of tables.
Row = one item (record)
Column = one piece of data (field)
Tables can reference each other so you can keep data organized (and avoid repeating the same info everywhere).
The database is the system of record (the source of truth).
The server is the safe gatekeeper between the UI and the database.
Most apps are just ‘query data’ + ‘show data’ repeated.
Where databases fit in a Wappler app
Section titled “Where databases fit in a Wappler app”Database stores data.
Server Connect reads/writes and enforces rules.
App Connect displays data and triggers actions.
So you typically don’t connect the browser directly to the database — the server sits in the middle as the safe gatekeeper.
Server Connect
Queries +
rules
rules
App Connect
Renders +
actions
actions
Browser shouldn’t talk directly to the database.
Server is the safe boundary: validate + authorize + query.
Client renders the results and triggers actions.
Think in tables
Section titled “Think in tables”A relational database is commonly organized like spreadsheets.
Table = a type of thing (users).
Row = one thing (one user).
Column = one property (email).
References and relationships
Section titled “References and relationships”TIP: In Wappler, Database Manager can set up references visually (so you can focus on the model, not the SQL details).
Reference
Connect tables
by IDs
by IDs
One-to-many
Customer →
many orders
many orders
Many-to-many
Use a link
table
table
A table can reference another table to connect related data.
One-to-many: one customer can have many orders.
Many-to-many: usually modeled with a separate link table.
Relationships reduce duplication and keep data consistent.
Queries (ask questions of data)
Section titled “Queries (ask questions of data)”Most apps need CRUD operations: select, insert, update, and delete.
This is what your server (Server Connect) does when your UI (App Connect) needs data.
Most features boil down to CRUD: create/read/update/delete (insert/select/update/delete).
The server runs queries, not the browser.
The UI asks for data; the server returns safe results.
Conclusion
Section titled “Conclusion”Databases are where your app’s long-term data lives: tables store records, and references connect related records. Next, we’ll walk through a first end-to-end flow: database → Server Connect API → page.
Store
Tables +
rows
rows
Relate
References
connect data
connect data
Flow
DB → API →
page
page
Database stores truth; server controls access.
References keep data organized and consistent.
Next: walk the full data flow end-to-end.
Continue
Section titled “Continue”Jump to the first data flow tour.