.png%3Falt%3Dmedia%26token%3D060e2220-39ef-4b8b-9dce-8688ff38e664)
.png%3Falt%3Dmedia%26token%3D060e2220-39ef-4b8b-9dce-8688ff38e664)
Database
The database is one of the core features of Deskree. For each project, we create a separate database instance with the following features:
- Automatically generated REST & GraphQL APIs with API documentation on the platform and in a form of postman collections. The data can also be accessed via our Javascript SDK.
- Each database is protected by middleware, where you are able to configure permissions for each endpoint as well as define the API rate limits.
Currently, we allow the creation of one database per project. However, soon users will be able to have an unlimited number of databases of various types (including MySQL, Postgres, etc.).
We do not limit the project based on the database size, number of columns, or other properties. You can have it as large or small as you prefer. For limitations, visit the Database Limitations page.
The database can be queried via the API interface that we provide in a form of REST, GraphQL, and Javascript SDK.
We allow exporting and importing of data in JSON or CSV format. For more information, visit Import / Export page.
Deskree permissions allow you to configure who can access what information within your back-end. Hence, to be able to limit data edits/deletes only to the original author of an object, we save the UID of the user who originally created that object in a
author column for each table. For more information visit the Permissions page.Yes, you can "link" one table to another by creating a column with
one-to-one or one-to-many reference data type. You will then be able to get this data via GraphQL Queries, or REST API and Javascript SDK using includes parameter.We save the UID(s) of the object(s) from another table that you referenced. You can get the full object that is referenced without making additional API requests via REST API using
includes query parameter or GraphQL Queries.Last modified 4mo ago