fw_branches
This is an old revision of the document!
Table of Contents
Purpose & Overview
The fw_branches table manages branch-related details for each client. Since a client can have multiple branches, this table ensures:
- Organized tracking of branch identity (name, unique code).
- Storage of location & website details (if applicable).
- Branding support through logos & invitation headers.
This table enables seamless handling of multiple branches under a single client while maintaining structured relationships.
Table Structure
| Column Name | Data Type | Description |
|---|---|---|
| id | Primary Key | Unique identifier for each branch (auto-incremented). |
| clientid | Foreign Key | References the fw_clients table (one client → many branches). |
| branchname | varchar(100) | Name of the branch. |
| branchcode | varchar(100) | Unique identifier/code assigned to the branch (must be unique). |
| 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: 110×100 pixels). |
| invitationheader | BLOB | Header image for invitations (Recommended: 120×32 pixels). |
Relationships
- clientid → References fw_clients table (Each branch belongs to one client).
- branchcode → Must be unique across all branches.
Example Data
| 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 | - | - |
Common Issues & Solutions
Issue: “Duplicate entry error for branchcode.” Solution: Ensure branchcode is unique across all branches.
Issue: “Foreign key constraint fails on clientid.” Solution: Verify that the clientid exists in fw_clients before inserting a branch.
Issue: “Null values for website or location.” Solution: These fields are optional and can be left NULL if no data is available.
Notes
- Each client can have multiple branches, each requiring a unique branchcode.
- Logos and invitation headers should follow the recommended dimensions.
fw_branches.1741237601.txt.gz · Last modified: 2025/03/06 05:06 by gloria