Model a many-to-many relationship between tables.
Recorded with an earlier Twidget interface. Names, control locations and available options may differ; use the linked documentation for current guidance.
Watch tutorial (3:51)
Model a one-to-many relationship between tables.
Recorded with an earlier Twidget interface. Names, control locations and available options may differ; use the linked documentation for current guidance.
Watch tutorial (2:10)In Twidget, you can connect database table data using the _id field that is automatically generated for every row in a table. This _id field is essential for creating and maintaining relationships across different tables.
A one-to-one relationship occurs when a single row in Table A is linked to a single row in Table B. Each record in Table A has a direct and unique relationship with a single record in Table B.
For example, consider a Users table and a Profiles table:
Each user in the Users table corresponds to a unique profile in the Profiles table.
The Profiles table will have a foreign key _user_id that references the _id field in the Users table.
A one-to-many relationship occurs when a single row in Table A is linked to multiple rows in Table B. Each record in Table A can have multiple related records in Table B, but each record in Table B has only one corresponding record in Table A.
For example, consider a Categories table and a Products table:
Each category in the Categories table can include multiple products from the Products table.
The Products table will have a foreign key _category_id that references the _id field in the Categories table.
A many-to-many relationship occurs when multiple rows in Table A are linked to multiple rows in Table B. Each record in Table A can have many corresponding records in Table B and vice versa.
For example, consider a Students table and a Courses table:
Each student can enroll in multiple courses.
Each course can have multiple students enrolled.
This relationship is typically implemented using a junction table, such as an Enrollments table, which contains foreign keys _student_id and _course_id that reference the _id field in the Students and Courses tables, respectively.
When working with functions in Twidget, you can use the _id fields to query related data and populate the complete data set into the main object.
Save Changes Together
A Database Transaction groups database work so its changes complete together. If a command in the block fails, the block's changes are rolled back. Example: an order and its stock change. 1. Add Database Transaction to the workflow. 2. Inside Save changes together, add the supported commands that cr...
Adding Database Table Rows
In Twidget, you can easily add new entries (rows) to your database tables. This feature allows you to expand your data dynamically without the need for complex coding. This document provides a step-by-step guide on how to add rows to your database tables. Adding a New Entry to a Table. To add a new ...
Database Change Triggers
Run an event automatically when a record is created, updated or deleted in a Twidget table. For example, send a welcome message after adding a customer, or refresh a summary when an order changes. Prepare the event. Create an event containing the steps you want to run. Add an Object input named `tri...
Authentication Table
An authentication table is a crucial component in Twidget that is used to store all necessary authentication information, essential for authenticating requests. Overview. - Purpose: To store authentication details such as email, password, token signature, and reset key. - Recommendation: It's recomm...
Summarise Records
Use Summarize Records when you need a summary rather than a list of every record. Create a summary. 1. Add Summarize Records to your workflow. 2. Choose the table and add filters if you only want some records. 3. Open Output and add a calculation. 4. Choose Count, Sum, Average, Lowest or Highest. 5....
