Run any Skill in Manus with one click

Get Started

mysql-lamp-legacy

Stars2

Forks1

UpdatedJanuary 23, 2026 at 19:25

Managing legacy MySQL/MariaDB schemas in LAMP stacks.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

sraloff

sraloff/gravityboots

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Database ArchitectsComputer and Mathematical Occupations·SOC 15-1243

SKILL.md

readonly

name	mysql-lamp-legacy
description	Managing legacy MySQL/MariaDB schemas in LAMP stacks.

MySQL / MariaDB (LAMP Legacy)

When to use this skill

Working on legacy LAMP (Linux, Apache, MySQL, PHP) projects.
Maintaining WordPress, Drupal, or older custom PHP apps.
Dealing with specific MySQL quirks (backticks, engine types).

1. Schema Management

Engine: Ensure InnoDB is used (not MyISAM).
Encoding: Convert/Ensure utf8mb4 (collation utf8mb4_unicode_ci or utf8mb4_0900_ai_ci).
Dates: Beware of 0000-00-00 dates; enable strict mode if possible (NO_ZERO_DATE).

2. Identifiers

Quoting: Use backticks ` ` for identifiers (tables, columns) if they conflict with keywords.
Case Sensitivity: Remember table names are case-sensitive on Linux but not Windows/macOS. Lowercase conventions prefered.

3. Optimization

Indexes: Max key length limits might apply on older versions with utf8mb4.
Query Cache: Deprecated/Removed in newer MySQL; do not rely on it.
Foreign Keys: Often missing in legacy apps; add them if InnoDB allows, otherwise enforce in app logic (but add a comment // Logic FK).

More from this repository

same repository

project-initialization-bootstrap

sraloff/gravityboots

Bootstraps a new project with standard folder structure, git init, basic files, planning doc skeletons, and initial memory.json. Triggers on new project creation keywords. CRITICAL for first-time setup.

2026-01-232

apache-lamp-config

sraloff/gravityboots

Configuration for Virtual Hosts, .htaccess, and PHP-FPM in LAMP stacks.

2026-01-232

api-design-patterns

sraloff/gravityboots

Principles for REST, GraphQL, versioning, and API authentication.

2026-01-232

assets-icons-fonts

sraloff/gravityboots

Optimization and usage of SVGs, fonts, and static assets.

2026-01-232

bootstrap-legacy

sraloff/gravityboots

Patterns for maintaining or migrating Bootstrap 3/4/5 projects.

2026-01-232

caddy-modern-config

sraloff/gravityboots

Caddyfile configuration, auto-HTTPS, and FastCGI.

2026-01-232

name	mysql-lamp-legacy
description	Managing legacy MySQL/MariaDB schemas in LAMP stacks.

MySQL / MariaDB (LAMP Legacy)

When to use this skill

Working on legacy LAMP (Linux, Apache, MySQL, PHP) projects.
Maintaining WordPress, Drupal, or older custom PHP apps.
Dealing with specific MySQL quirks (backticks, engine types).

1. Schema Management

Engine: Ensure InnoDB is used (not MyISAM).
Encoding: Convert/Ensure utf8mb4 (collation utf8mb4_unicode_ci or utf8mb4_0900_ai_ci).
Dates: Beware of 0000-00-00 dates; enable strict mode if possible (NO_ZERO_DATE).

2. Identifiers

Quoting: Use backticks ` ` for identifiers (tables, columns) if they conflict with keywords.
Case Sensitivity: Remember table names are case-sensitive on Linux but not Windows/macOS. Lowercase conventions prefered.

3. Optimization

Indexes: Max key length limits might apply on older versions with utf8mb4.
Query Cache: Deprecated/Removed in newer MySQL; do not rely on it.
Foreign Keys: Often missing in legacy apps; add them if InnoDB allows, otherwise enforce in app logic (but add a comment // Logic FK).