INTEGER
type, it likely serves as the primary key for the table. Each region is uniquely identified by this ID.VARCHAR(9)
type, it stores the name of the region, up to 9 characters in length.regions table preview:
region_id | region_name |
---|---|
1 | Africa |
2 | America |
3 | Asia |
4 | Europe |
5 | Oceania |
INTEGER
type that identifies the customer. This field links to customer-related data, probably serving as a foreign key in other tables.INTEGER
type that connects the customer to a specific region. It is a foreign key referencing the region_id
in the regions
table.INTEGER
type, likely used to identify a specific node or account for the customer.DATE
type that indicates when the customer node became active.DATE
type that indicates when the customer node was deactivated or ended.Customer_nodes table preview:
customer_id | region_id | node_id | start_date | end_date |
---|---|---|---|---|
1 | 3 | 4 | 2020-01-02 | 2020-01-03 |
2 | 3 | 5 | 2020-01-03 | 2020-01-17 |
3 | 5 | 4 | 2020-01-27 | 2020-02-18 |
4 | 5 | 4 | 2020-01-07 | 2020-01-19 |
5 | 3 | 3 | 2020-01-15 | 2020-01-23 |
6 | 1 | 1 | 2020-01-11 | 2020-02-06 |
7 | 2 | 5 | 2020-01-20 | 2020-02-04 |
8 | 1 | 2 | 2020-01-15 | 2020-01-28 |
9 | 4 | 5 | 2020-01-21 | 2020-01-25 |
10 | 3 | 4 | 2020-01-13 | 2020-01-14 |
INTEGER
type that identifies the customer involved in the transaction. This is a foreign key linking to the customer_nodes
table.DATE
type that records the date of the transaction.VARCHAR(10)
type that categorizes the type of transaction (e.g., deposit, withdrawal, purchase).