When you already have a database running, or would prefer to manage your database separately, using PostgreSQL or MySQL is a great way to start. You can add external database connections through the Budibase interface with a few clicks.
To add a new remote datasource choose the Data tab in Budibase , then click the
Add source button.
You'll be prompted to choose the type of datasource you want. Next you will fill out the settings for your chosen SQL database. See each SQL datasource page for specific settings.
I each case, you will have the option to
Save and fetch tables,
Skip table fetch, or go
Back and select a different datasource.
Your database server will need to be whitelisted in any firewalls protecting your database. If you are using the Budibase Cloud you should Whitelist the Budibase IP addresses in your firewall. If you are self-hosting you should whitelist the IP address of your Budibase server on your database server.
If you use Docker to host your own Budibase installation and are connecting to a database on the same machine as your Budibase installation you should set the host to
172.17.0.1(if running on Linux).
By default when you add a new datasource, the tables will be fetched after the connection has been confirmed. However, in the dialog where you configure a new datasource, you can skip fetching tables.
Fetching tables can also be triggered at any stage after the source has been added. This is especially useful when you've added, removed, or updated a new table after you've added the connection to Budibase.
To fetch tables, head over to the added datasource in the sidebar, and scroll past the configuration of the data source.
Assuming you skipped the table fetch on initial setup, it can be useful to fetch only the tables you need. Perhaps the database has a large number of tables and you don't want to pull them all in for your Budibase app.
Another reason may be to prevent changes to certain tables being overwritten in Budibase; particularly Formula columns.
To fetch a subset of your database tables, click
Fetch tables and then toggle
Fetch listed tables only. This will present a box where you can enter the names of the tables you want to fetch.
To help Budibase understand your database you will need to create relationships between the different tables. This can be done from the configuration screen of your datasource. To get there, click your datasource in the sidebar and scroll down until you find the Relationships section.
When you click the
Define relationship button, you get a form in which you can define the relationship.
When you define a one-to-one or one-to-many relationship you'll need to pick the "One" relation type. Then you will have to choose the from table and its primary key column. After that, you need to choose the to table and the foreign key column. For example, if you have a pets table, and an owner table, you first will have to select the owner primary index, and then select the pets "owner" foreign key column.
After setting this up, an
owner_id column will be added to the
pets table, as well as a
pets column to be added to the
owner table. These columns will only be added internally, meaning this column will not be added to the remote datasource. This is to allow Budibase to keep track of the relationships without interfering with the remote source. Visually, when you navigate to both tables, you'll see the relations displayed as blocks referring to the related row in the other table.
If you want to change the field being used in the relationship tags, you can do this by selecting the display column in each table.
With a many-to-many relationship, a joining table will be needed. The steps will be similar to the above, however a "through" table needs to be selected.
This "through" table will be the joining table.
This can be useful, for example, if you had many students in many classes.
When saving rows, you will not need to save entries to the joining table - Budibase will automatically do this for you.
After you have defined relationships, you will see them listed in the Relationships section of the datasource.
To edit a relationship, simply click on an entry. You will then be able to change the keys and tables involved, or
Delete the relationship. This will automatically remove any previous columns that were created for handling the relationships in both tables.
Updated about 13 hours ago