fw_branches
This is an old revision of the document!
Table of Contents
Introduction
This table stores details about various branches associated with clients. Each client can have multiple branches, and this table captures essential branch-specific information such as:
- Branch name and unique code
- Geographical location and website
- Branding elements (logos, invitation headers)
This structure ensures efficient data organization, making it easy to manage multiple branches under a single client.
Table Structure
| Column Name | Data Type | Description |
|---|---|---|
| id | Primary Key | Unique identifier for each branch (auto-incremented). |
| clientid | Foreign Key | References the client this branch belongs to (one client → many branches). |
| branchname | varchar(100) | Name of the branch. |
| branchcode | varchar(100) | Unique identifier/code assigned to the branch. |
| location | varchar(100) | Geographical location or address of the branch. |
| website | varchar(100) | Website URL of the branch (if applicable). |
| questionnairelogo | BLOB | Logo used in questionnaires (recommended size: 110×100 pixels). |
| invitationheader | BLOB | Header image for invitations (recommended size: 120×32 pixels). |
Example Data
Below is an example dataset showcasing different branches under a single client:
| id | clientid | branchname | branchcode (Unique) | location | website |
|---|---|---|---|---|---|
| 5 | 1 | Swietelsky | 3 | ||
| 3 | 1 | Zevenaar-Didam | 1 | ||
| 4 | 1 | Groningen Spoorzone | 2 | ||
| 6 | 1 | EdesPoort | 4 | ||
| 7 | 1 | Leeuwarden | 4554 | ||
| 8 | 1 | Maaslijn | 4848 |
Notes: - Each client can have multiple branches. - Ensure branchcode remains unique for proper identification. - If a website or location is unavailable, it can be left null.
fw_branches.1741236994.txt.gz · Last modified: 2025/03/06 04:56 by gloria