ワンクリックでManusで任意のスキルを実行

system-database-schema-updates

スター4

フォーク0

更新日2026年4月29日 15:11

Use when creating or modifying database schema in Zolinga modules, including install SQL and update migration scripts with naming conventions.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

webdevelopers-eu

webdevelopers-eu/zolinga

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Zolinga Database Schema Updates

Use When

Creating new schema objects.
Updating existing tables, views, or indexes.

See also: system-install-scripts — covers the full install-vs-update lifecycle, naming, ordering, and the rule that install scripts must stay complete while update scripts must only be added. Essential reading before creating any install or update script.

Critical: Always Bump Module Version

Any schema change — adding an update script, modifying install SQL, or altering any install/ artifact — requires bumping the module version in zolinga.json. The system detects version changes to trigger the install/update pipeline. Without a version bump, new update scripts will never execute on existing installations.

Workflow

Use camelCase for DB table names, field names, and aliases (e.g. rmsUsers, cronJobs, ipdAccounts, trialStart, subscriptionEnd).
Prefix every table name with the module abbreviation (e.g. ipd for ipdefender, rms for zolinga-rms, cron for zolinga-cron). The prefix is derived from the module folder name, shortened to a short lowercase identifier. Examples: ipdAccounts, ipdWatchlist, rmsUsers, cronJobs.
Put initial install SQL in modules/<module-name>/install/install/*.sql.
Put incremental schema updates in modules/<module-name>/install/update/*.sql.
Use $api->db (query, queryExpand) from PHP code for DB access.
Bump the module version in modules/<module-name>/zolinga.json (e.g. "version": "1.3" → "1.4"), then run bin/zolinga (no parameters) to trigger the install/update pipeline.

Idempotency (IF NOT EXISTS / IF EXISTS)

All DDL statements that support IF NOT EXISTS or IF EXISTS must use them so scripts are safe to run multiple times without failing:

CREATE TABLE IF NOT EXISTS ...
CREATE VIEW IF NOT EXISTS ...
CREATE INDEX IF NOT EXISTS ... (MySQL 8.0+; for older versions, check existence first)
ALTER TABLE ... ADD COLUMN IF NOT EXISTS ... (MySQL 8.0+; for older versions, use a separate check)
DROP TABLE IF EXISTS ...
DROP VIEW IF EXISTS ...
DROP INDEX IF EXISTS ... (MySQL 8.0+)

For MySQL versions that do not support IF NOT EXISTS on a given statement (e.g. ADD COLUMN before 8.0), wrap the operation in a conditional check using a DO block or a stored procedure that queries INFORMATION_SCHEMA.

Validation

Ensure update scripts are additive and ordered.
Ensure schema changes map to expected model/query usage.

Documentation Abstract

Start with Module Installation and Updates.md for install/update lifecycle.
Use PHP Installation Scripts.md for mixed SQL/PHP installation flows.
Use Configuration.md when schema behavior is controlled by config values.

References

system/wiki/Zolinga Core/Module Installation and Updates.md
system/wiki/Zolinga Core/Module Installation and Updates/PHP Installation Scripts.md
system/wiki/ref/event/install.md
system/wiki/ref/event/system/install/script/php.md
system/wiki/ref/event/system/install/script/wildcard.md
system/wiki/Zolinga Core/Configuration.md

このリポジトリの他の Skills

同じリポジトリ

system-create-mcp-resource

webdevelopers-eu/zolinga

Use when creating or updating MCP resources — static files exposed to MCP clients via `resources/list` and `resources/read`. Covers `.meta.json` descriptors, URI rewriting, dynamic resources via `mcp:resources/list` event hook, and the `mcp-system` scheme.

2026-07-224

system-convert-remote-event-to-mcp-tool

webdevelopers-eu/zolinga

Use when exposing an existing `origin: ["remote"]` listener as an MCP tool without rewriting the handler. Covers the one-line manifest pattern that re-uses the same class+method, plus the minimal schema work needed to satisfy `McpToolsListHandler::collectTools()`. Complements system-create-mcp-tool (which covers the greenfield case).

2026-07-214

system-create-mcp-tool

webdevelopers-eu/zolinga

Use when exposing a Zolinga event handler as an MCP (Model Context Protocol) tool — i.e. a method clients can invoke via JSON-RPC `tools/call`. Covers handler class, manifest binding, JSON Schemas, the `Tools\CallEvent` contract, and the `schema.response` requirement enforced by `McpToolsListHandler::collectTools()`.

2026-07-214

system-events-client

webdevelopers-eu/zolinga

Use when working with the JavaScript client-side event system in Zolinga. Covers the Event class, Api gateway, dispatching events from JS to PHP, receiving broadcastBack responses, inter-component communication via BroadcastChannel, and web component integration.

2026-07-154

system-translations

webdevelopers-eu/zolinga

Use when adding localized strings in PHP or HTML, including gettext usage patterns and context-aware translation strings for Zolinga Intl.

2026-07-064

system-php-coding-style

webdevelopers-eu/zolinga

Use when writing or reviewing PHP code in this repository to enforce strict typing, naming, file layout, and listener/service interface conventions.

2026-06-274

Zolinga Database Schema Updates

Use When

Creating new schema objects.

Updating existing tables, views, or indexes.

See also: system-install-scripts — covers the full install-vs-update lifecycle, naming, ordering, and the rule that install scripts must stay complete while update scripts must only be added. Essential reading before creating any install or update script.

Critical: Always Bump Module Version

Workflow

Use camelCase for DB table names, field names, and aliases (e.g. rmsUsers, cronJobs, ipdAccounts, trialStart, subscriptionEnd).

Prefix every table name with the module abbreviation (e.g. ipd for ipdefender, rms for zolinga-rms, cron for zolinga-cron). The prefix is derived from the module folder name, shortened to a short lowercase identifier. Examples: ipdAccounts, ipdWatchlist, rmsUsers, cronJobs.

Put initial install SQL in modules/<module-name>/install/install/*.sql.

Put incremental schema updates in modules/<module-name>/install/update/*.sql.

Use $api->db (query, queryExpand) from PHP code for DB access.

Bump the module version in modules/<module-name>/zolinga.json (e.g. "version": "1.3" → "1.4"), then run bin/zolinga (no parameters) to trigger the install/update pipeline.

Idempotency (IF NOT EXISTS / IF EXISTS)

All DDL statements that support IF NOT EXISTS or IF EXISTS must use them so scripts are safe to run multiple times without failing:

CREATE TABLE IF NOT EXISTS ...

CREATE VIEW IF NOT EXISTS ...

CREATE INDEX IF NOT EXISTS ... (MySQL 8.0+; for older versions, check existence first)

ALTER TABLE ... ADD COLUMN IF NOT EXISTS ... (MySQL 8.0+; for older versions, use a separate check)

DROP TABLE IF EXISTS ...

DROP VIEW IF EXISTS ...

DROP INDEX IF EXISTS ... (MySQL 8.0+)

Validation

Ensure update scripts are additive and ordered.

Ensure schema changes map to expected model/query usage.

Documentation Abstract

Start with Module Installation and Updates.md for install/update lifecycle.

Use PHP Installation Scripts.md for mixed SQL/PHP installation flows.

Use Configuration.md when schema behavior is controlled by config values.

References

system/wiki/Zolinga Core/Module Installation and Updates.md

system/wiki/Zolinga Core/Module Installation and Updates/PHP Installation Scripts.md

system/wiki/ref/event/install.md

system/wiki/ref/event/system/install/script/php.md

system/wiki/ref/event/system/install/script/wildcard.md

system/wiki/Zolinga Core/Configuration.md

name	system-database-schema-updates
description	Use when creating or modifying database schema in Zolinga modules, including install SQL and update migration scripts with naming conventions.
argument-hint	<module-name> [table-or-view]