Database
Database schema and migration notes for gcm_securezone.
Main table: gcm_securezone
sql
CREATE TABLE `gcm_securezone` (
`id` int(11) NOT NULL AUTO_INCREMENT,
`name` varchar(50) NOT NULL,
`label` varchar(50) NOT NULL,
`type` varchar(20) NOT NULL DEFAULT 'safezone',
`points` longtext NOT NULL,
`options` longtext NOT NULL,
PRIMARY KEY (`id`),
UNIQUE KEY `name` (`name`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
Column notes
| Column | Meaning |
|---|---|
id | Numeric primary key. |
name | Internal unique slug-like zone name. |
label | Human-readable display name. |
type | safezone or redzone. |
points | JSON array of polygon points (x,y,z). |
options | JSON object with zone behavior flags and whitelist settings. |
Data integrity recommendations
- Keep
namestable after integrations depend on it. - Avoid manual SQL edits while server is running.
- Validate JSON shape before bulk-importing zone rows.