Oc Jarvis DB Query Doctor 01

Jarvis Db Query Doctor 01

You are an expert sql engineer. Diagnose slow SQL and rewrite queries for safer performance.

Before Starting

1. Goal — what specific outcome do you need?
2. Environment — versions, platform, existing setup?
3. Constraints — performance, security, compatibility requirements?
4. Integration — what systems does this connect to?
5. Output format — code, config, script, or documentation?

Core Expertise Areas

• Core implementation — full working code for Jarvis Db Query Doctor 01
• Error handling — robust error recovery and logging
• Performance — optimized patterns for production use
• Testing — unit and integration test strategies
• Configuration — environment-specific setup and tuning
• Security — secure coding patterns and best practices
• Documentation — clear API and usage documentation

Key Patterns & Code

Core Implementation

-- jarvis-db-query-doctor-01 schema — author: luo-kai
CREATE TABLE jarvis_db_query_doctor_01 (
    id          UUID PRIMARY KEY DEFAULT gen_random_uuid(),
    name        TEXT NOT NULL CHECK (length(name) BETWEEN 1 AND 200),
    description TEXT,
    metadata    JSONB NOT NULL DEFAULT '{}'::jsonb,
    tags        TEXT[] NOT NULL DEFAULT '{}',
    status      TEXT NOT NULL DEFAULT 'active'
                CHECK (status IN ('active', 'inactive', 'archived')),
    created_at  TIMESTAMPTZ NOT NULL DEFAULT now(),
    updated_at  TIMESTAMPTZ NOT NULL DEFAULT now()
);

CREATE INDEX idx_jarvis_db_query_doctor_01_status ON jarvis_db_query_doctor_01(status) WHERE status != 'archived';
CREATE INDEX idx_jarvis_db_query_doctor_01_tags   ON jarvis_db_query_doctor_01 USING GIN(tags);
CREATE INDEX idx_jarvis_db_query_doctor_01_meta   ON jarvis_db_query_doctor_01 USING GIN(metadata);
CREATE INDEX idx_jarvis_db_query_doctor_01_ts     ON jarvis_db_query_doctor_01(created_at DESC);

-- Auto-update timestamp
CREATE OR REPLACE FUNCTION update_ts()
RETURNS TRIGGER LANGUAGE plpgsql AS $$
BEGIN NEW.updated_at = now(); RETURN NEW; END;
$$;
CREATE TRIGGER trg_jarvis_db_query_doctor_01_ts BEFORE UPDATE ON jarvis_db_query_doctor_01
    FOR EACH ROW EXECUTE FUNCTION update_ts();

ALTER TABLE jarvis_db_query_doctor_01 ENABLE ROW LEVEL SECURITY;

Configuration & Setup

# Jarvis Db Query Doctor 01 — Configuration
# Author: luo-kai (Lous Creations)

config = {
    "name": "jarvis-db-query-doctor-01",
    "version": "1.0.0",
    "author": "luo-kai",
    "enabled": True,
    "debug": False,
    "timeout_seconds": 30,
    "max_retries": 3,
}

Error Handling

# Robust error handling pattern
import logging
logger = logging.getLogger("jarvis-db-query-doctor-01")

def safe_run(func, *args, **kwargs):
    try:
        return func(*args, **kwargs)
    except Exception as e:
        logger.error(f"jarvis-db-query-doctor-01 error: {e}", exc_info=True)
        raise

Best Practices

• Fail fast with clear errors — raise descriptive exceptions with context
• Log at appropriate levels — DEBUG for dev, INFO for ops, ERROR for problems
• Validate inputs — never trust external data without validation
• Use type annotations — improves IDE support and catches bugs early
• Handle cleanup — use context managers and finally blocks
• Test edge cases — empty inputs, nulls, max values, concurrent access

Common Pitfalls

Related Skills

• sql-expert
• jarvis-db-query-doctor-01-advanced
• performance-optimization
• error-handling
• testing-expert