⌘ SchemaMap

Map a PHP method’s database tables with Codex

PHP method → a local agent with permitted source access → tables and JOIN evidence → a saved SchemaMap task sheet.

SchemaMap 0.14.0 · Updated · The editor uses Russian UI labels, shown as written.

    The agent investigates the source

    For a developer tracing a request through a PHP application. You need a precise method, a repository accessible to a permitted local Codex, schema metadata and a SchemaMap connection with appropriate permissions. A website link alone neither shares source code with SchemaMap nor starts repository analysis.

    From method to sheet

    1. Ask the local agent to read the method and called code in its permitted environment.
    2. Request discovered tables, JOINs and evidence: file, line, SQL or query name. Separate hypotheses from findings.
    3. Use schema_search/table_get to match names to exact IDs in the selected area.
    4. Read the task and revision. Create or update a sheet using the current REST/MCP contract.
    5. Open «+ JOIN», inspect evidence on the right and append findings to the task journal.

    The result is a reopenable method map with relationship provenance. Submitted snippets must be permitted for storage in the area.

    Validate findings

    Dynamic SQL, branches and ORMs may limit static analysis completeness. The agent must not invent FKs from similar names. SchemaMap stores SQL as text without executing it. The downloadable research worker is read-only; registering an agent without a running process does not produce background answers. The demo illustrates maps, while real PHP analysis requires your own permitted environment.