Developer Builds Tool for Realistic Relational Database Generation

Tool Solves Database Generation Problem for App Development
A developer on r/ClaudeAI shared their solution to a common problem when building apps with Claude Code: the need for realistic, fully loaded relational databases for testing and demos. While prompting Claude worked for small datasets, generating larger datasets with intact foreign key relationships became messy.
Technical Approach That Worked
The developer built a tool with several key technical approaches:
- Topological generation: The system resolves the foreign key dependency graph and generates tables in the correct order—parent tables first, then children—with every foreign key pointing to a real parent row.
- Cardinality modeling: Instead of uniform distributions, the generator uses distributions matching real-world patterns. For example, order counts per user follow a negative binomial distribution, and activity timestamps cluster around business hours with realistic seasonal variation. The system infers these patterns from schema structure and column names without requiring configuration.
- Cross-table consistency: The system handles implicit business rules not declared as foreign key constraints, such as ensuring payment dates come after invoice dates, or that an employee's department and salary match their job title in the appropriate currency. These rules are inferred from naming conventions and table relationships.
- Schema from plain English: Users describe what they need (e.g., "a SaaS app with organizations, users, projects, tasks, and an activity log") and the tool builds the full schema with all relationships, column types, and constraints, then generates the data in one shot.
Development Context
The developer noted that while the application was coded with Claude Code, the generation engine itself—the part that solves the constraint graph and models distributions—had to be architected manually. They found that 100% reliance on LLMs for generating this data was not scalable nor reliable enough.
The developer is now working on building MCP (Model Context Protocol) to work with Claude.
📖 Read the full source: r/ClaudeAI
👀 See Also

LM Studio parser bugs break Qwen3.5 tool calling and reasoning
LM Studio's server parser has three interacting bugs that silently break tool calling, corrupt reasoning output, and make models appear worse than they are. The issues affect reasoning models like Qwen3.5 and DeepSeek-R1, with one bug reported over a year ago still unresolved.

SeeFlow: Architecture Diagrams That Are Wired to Your Live App
SeeFlow generates a flow canvas from your codebase and wires each node to your actual running app, with plugins for Claude Code, Codex, Cursor, Windsurf, and an MCP server.

devopsiphai: Open-source Claude Code skill audits operational health across 6 phases
devopsiphai is an open-source Claude Code skill that audits production project operability using a 6-phase process and ARC framework, outputting letter grades and a structured TODO.md with effort-estimated tasks.

OpenGauge: Open-source tool for tracking LLM agent costs locally
OpenGauge is an open-source tool that monitors API calls from LLM agents like OpenClaw, logging token usage, costs, and latency to a local SQLite database. It includes proxy mode for automatic logging, detailed cost statistics, and circuit breaker functionality to prevent runaway loops.