RumataWork with databases
Store structured information, understand tables, and inspect database health.
Step-by-step guidance.
Before you start
Understand tables and records
A database stores structured information that your product needs to remember. A table groups one kind of information, such as requests. Each row is one record. Columns describe its fields, such as title, due date, and status.
| Term | In the request portal |
|---|---|
| Table | requests |
| Row | One client request |
| Column | title or status |
| Identifier | A stable value that identifies a specific request |
| Relationship | A request belongs to a particular client |
Inspect your data
- Open Database in your factory’s product tools. Check the status before trying to query it.
- Browse the available tables. Select a table to inspect its columns and sample rows.
- Choose the table, diagram, query builder, or SQL view for the information you want to inspect.
- If you are new to databases, ask Rumata to explain the table structure and propose a read-only query.
- Verify that the result belongs to the project and users you expected.
Describe the information your app needs
For each request, store a title, description, due date, status,
and the client who submitted it.
Explain the tables and relationships before changing the database.
Clients must only be able to read their own requests.Access rules need backend enforcement. A filtered list in the frontend does not protect records from direct requests. Coordinate schema changes with the backend services, workflows and screens that read those fields.
Starting, idle, and degraded states
Wait for a hosted database to start or wake before running operations. Check its state and recovery controls in Database. Startup delays, failed SQL statements, and a degraded state have different causes, so use the diagnostic information for the reported state.
Capacity and idle behavior depend on your account’s entitlement. Check Usage (opens in a new tab) and the database status message when writes fail or a database cannot start. Do not repeatedly recreate a database to troubleshoot availability.
Recovery and retention
Use the database recovery controls only after checking the scope, available recovery points, and the expected effect on later data. Recovery windows depend on the plan and current operational state. Retain independent exports when your business requires them.