This data source is the one that is native to Budibase. Any data you add here is stored directly on your Budibase instance.
You can create a table when you're in the
data section in your application.
The recommended flow is to go to your Budibase DB instance from the sidebar, and then click the
Create Table button. A shortcut to this is when you press the
+ button on the top left and choose Budibase DB.
When creating a new Budibase DB table you can choose which built-in (auto types) columns you want to have. Each of these will be automatically maintained, created and updated based on the properties. You can choose to omit as you see fit. These can be added post-creation too through the "Create Column" method.
An automatically generated ID
The user who created the row
When this row was created
The user who updated the row last
The time when the row was updated last
When you already have existing data, you can import this using a CSV file when creating a table. This will automatically identify columns and create them for you, after which you can specify data types per column.
In the example below I imported a CSV with 4 columns representing a table of countries. After the file uploaded the screen below was shown.
As you can see, it automatically identified the 4 columns and allowed me to pick the data types for each column.
To add new columns to an existing Budibase DB table, navigate to the table you want to edit, then click the
Create Column button on top of the table. This will display a dialog where you can configure the column you want to add.
- Step into the table through the sidebar
- Hover over the column name you want to edit
- Click the pencil icon
The display column is an important aspect when you're setting up relationships in tables. The column you select as a display column will be the one visually displayed inside a relationship column in another table.
Selecting a column during the table creation is only possible if you import data using a
CSV file. To select a display column in any other situation, edit the column you want to make the display. This will give you the Use as table display column option as shown below.
Within Budibase DB there are several data types to choose.
Storage of (relatively) short text
Long Form Text
Allows you to store large amounts of texts, also supports markdown
Predefined list of options of which one can be selected
Predefined list of options of which multiple can be selected
Storage of number
Storage of true/false
Storage of a date with a time
Storage of a file. Limited to 20MB per file
Creates a link between this table and another table
Allows you to store JSON within a row, with the option to define a schema
Auto columns can be added post-creation of the database by selecting data type.
Common column options:
The name of the column, used for querying and displaying
The type of data you want to store.
Use as table display column
Enabling this will make the newly created column the display column. This will also automatically make the field required
Enabling this allows you to search in this field
When primary index is in use, you can enable a second index for searching
Data type specific column options:
Enable Rich Text Format Support
Enabling this will allow you to store markdown
Long Form Text
The select-able options available for this column, one per line.
Allow a relationship to the specified table
Column name in other table
The relationship created will also be visible in the related table, this will set the new column name on the related table
The following column constraints are available:
When enabled, a value must be set for this field
The maximum length that can be stored in this column
When set, any value entered in the database lower than this number will be rejected
When set, any value entered in the database higher than this number will be rejected
When set, any date before the specified date is rejected for new rows
When set, any date after the specified date is rejected for new rows
External datasource constraints
You can add Budibase constraints to external table columns, however this is entirely for form validation and will not restrict the data that is saved.
Instead, you must add data constraints yourself to any external table schemas.
Updated 3 months ago