customers
| name | plan | |
|---|---|---|
| Mina Cho | [email protected] | pro |
| Jonah Hale | [email protected] | starter |
| Priya Shah | [email protected] | pro |
| Northwind Supply | [email protected] | team |
GEThttps://example-project.api.cubibase.com/rest/v1/customers
Tables and columns
A new table needs a name, one primary key, and up to 64 columns. You can add a column later. You cannot add a primary key later, and you cannot drop the primary key or the user column used for row policies.
Supported types are uuid, text, integer, bigint, boolean, timestamptz, jsonb, numeric, and double precision. Defaults can be gen_random_uuid(), now(), true, or false.
Rows, filters, and sorting
The row browser lists a table with the same filter, select, and order syntax as the Data API. Owners and admins can insert, update, and delete rows from the Console. A developer membership can read. These calls use the SQL role, so they are project-administration operations, not end-user requests.
The SQL editor stays read-only
- One statement, at most 8,000 characters.
- It must start with select, with, explain, show, values, or table.
- The transaction is read-only, with a statement timeout of a few seconds.
- The response includes at most 200 rows and says when the result was truncated.
Use the editor to inspect data. Use the table API when you need a new column.
Questions
Can I paste a migration file into the SQL editor?
No. The editor rejects anything that is not a single read-only statement. Schema changes go through the table endpoints the Console uses.
Will the row browser show every end user’s rows?
The Console uses the SQL role, whose table policy allows the developer to manage rows in the project. Application users are limited by the API role and the user-column policy. Those are different paths.