Fireapis lets you to add tables without any restriction, we also supports different type of relation link between tables in the particular environment

Tables which is created inside a environment will be always specific to thart environment. You wont be able to use it any other tables.

We use postgresql database to manage all your data. Whatever postgres supports the same functionality we will be supporting and keep improving.

All the timestamp related field will be stored in UTC timezone

Below are the common column types supported in tables:

  1. Text - Store a text or string value, for ex: fireapis no-code backend.

  2. Number- Store only a integer like a whole number for eg: 22, 23. Decimal number is not accepted in this column type for eg: 22.30, 23.54.

  3. Number with decimal - Store a decimal numbers for eg: 22.32, 23.12. Mostly we can use this type of column for pricing, or weighted quantites, etc.

  4. Boolean - Store only a true or false value, text or numner will not be accpeted.

  5. Date & Time - Store a timestamp with date and time along with it. For ex: 2024-05-15T14:07:10.619Z.

  6. Url - Store only url type column for eg:

  7. Ip Address - Stored only text format which should be in ip formate for eg:

  8. Date - Store a timestamp which will date only time will be always 00:00:00. With this field you wont be able to retreive time. Example input 2024-05-15T14:07:10.619Z which takes only date from it and stores it

  9. Time - Stores a timestamp which will have time only and here date will not be stored. This field always return time when retreived. Example input 2024-05-15T14:07:10.619Z which takes only time from it and stores it

  10. Reference other table - Store a relation between other tables. Lean more about table relationship and their purposes on our blog. Types of relation supported by fireapis:

    • One to One:

      This type of relation will be useful: First case, if you want to link user with their profile. In this case your can link your user table with profile as user will always going to have one profile Second case, if you have orders which always contains one customer in this case, then. you can link the customer as one to one with orders table.

    • Many to One: This type of relation will be useful: First case, If a order will have many menu items to it, then we can have menu items table linked to orders. Second case, if a user has many conversation ,then conversation table will be a many to one relation with users

We can see more about relation of tables and their implementation in detail in our blog.

Last updated