AI suggested using Supabase and PostgreSQL for my users and orders; how is that different from saving files?
| id | Name |
|---|---|
| u_42 | Lin |
orders.user_id → users.idAn order’s user ID must match an existing user| id | user_id |
|---|---|
| #1001 | u_42 |
Only user u_42 exists, but order #1002 references u_88. Predict whether it can be saved.
Software, data and instructions: A Database stores organized data; PostgreSQL is the software managing it; SQL is the language used to query, write and define constraints. The backend executes instructions through a database connection and the page displays the result.
Configure rules for the business: A foreign key checks whether the referenced user exists. Use a Transaction separately when order creation and stock deduction must commit together. A valid reference does not grant access; the backend still checks ownership and permission.
Separate built-in features from extensions: PostgreSQL supports tables, indexes and JSON queries. Vector similarity search can be provided by extensions such as pgvector, which must be installed or enabled by the host and are not present in every instance by default.
Store users and orders in PostgreSQL and add a foreign key for each order’s user ID. Try existing and nonexistent user IDs; verify that the first saves and the second is rejected without leaving an order.