Convert Markdown to SQL

Why Convert Markdown to SQL?

Converting Markdown to SQL is valuable when you have tabular data documented in Markdown tables that needs to be imported into a relational database. Markdown tables on GitHub, in documentation, or in project notes often contain structured data that can be transformed into SQL INSERT statements, CREATE TABLE scripts, or complete database migration files.

Markdown, created by John Gruber in 2004, is widely used for documenting data structures, API responses, and sample datasets. GitHub Flavored Markdown (GFM) supports tables that present data in a readable format. However, this data cannot be directly loaded into a database without first converting it to SQL statements that databases understand.

SQL (Structured Query Language), developed at IBM in the 1970s, is the universal language for relational databases. Converting Markdown tables to SQL produces ready-to-execute scripts with CREATE TABLE statements (inferring column types from data), INSERT statements for each row, and proper escaping of string values. The output is compatible with MySQL, PostgreSQL, SQLite, SQL Server, and other major database systems.

This conversion is especially useful for developers who document seed data in Markdown, teams that maintain data dictionaries in project documentation, and anyone who needs to quickly populate a database from tabular data in documentation files.

Key Benefits of Converting Markdown to SQL:

• Database Import: Generate ready-to-execute SQL scripts from Markdown tables
• Schema Generation: Automatic CREATE TABLE from column headers
• Seed Data: Convert documented sample data to INSERT statements
• Cross-Database: Output compatible with MySQL, PostgreSQL, SQLite
• Data Migration: Move data from documentation to live databases
• Test Fixtures: Generate test data scripts from documentation
• Proper Escaping: Strings properly quoted to prevent SQL injection

Practical Examples

Example 1: User Table to SQL

Input Markdown file (users.md):

# Users Table

| id | name      | email              | role    |
|----|-----------|--------------------|---------|
| 1  | Alice     | [email protected]  | admin   |
| 2  | Bob       | [email protected]    | editor  |
| 3  | Charlie   | [email protected]   | viewer  |

Output SQL file (users.sql):

-- Users Table
CREATE TABLE users (
  id INTEGER,
  name VARCHAR(255),
  email VARCHAR(255),
  role VARCHAR(255)
);

INSERT INTO users (id, name, email, role) VALUES
  (1, 'Alice', '[email protected]', 'admin'),
  (2, 'Bob', '[email protected]', 'editor'),
  (3, 'Charlie', '[email protected]', 'viewer');

Example 2: Product Catalog to SQL

Input Markdown file (products.md):

## Product Catalog

| sku     | product_name  | price  | stock |
|---------|---------------|--------|-------|
| SKU-001 | Widget A      | 9.99   | 150   |
| SKU-002 | Widget B      | 19.99  | 75    |
| SKU-003 | Gadget C      | 49.99  | 30    |

Output SQL file (products.sql):

-- Product Catalog
CREATE TABLE product_catalog (
  sku VARCHAR(255),
  product_name VARCHAR(255),
  price DECIMAL(10,2),
  stock INTEGER
);

INSERT INTO product_catalog (sku, product_name, price, stock) VALUES
  ('SKU-001', 'Widget A', 9.99, 150),
  ('SKU-002', 'Widget B', 19.99, 75),
  ('SKU-003', 'Gadget C', 49.99, 30);

Example 3: Configuration Data to SQL

Input Markdown file (settings.md):

## Application Settings

| key            | value        | description              |
|----------------|--------------|--------------------------|
| app.name       | MyApp        | Application display name |
| app.version    | 2.1.0        | Current version          |
| debug.enabled  | false        | Debug mode toggle        |

Output SQL file (settings.sql):

-- Application Settings
CREATE TABLE application_settings (
  key VARCHAR(255),
  value VARCHAR(255),
  description VARCHAR(255)
);

INSERT INTO application_settings (key, value, description) VALUES
  ('app.name', 'MyApp', 'Application display name'),
  ('app.version', '2.1.0', 'Current version'),
  ('debug.enabled', 'false', 'Debug mode toggle');

Frequently Asked Questions (FAQ)

Q: How are Markdown tables converted to SQL?

A: Markdown table headers become column names in a CREATE TABLE statement, and each table row becomes an INSERT statement. The converter analyzes the data to infer appropriate SQL data types (INTEGER for numbers, DECIMAL for decimal values, VARCHAR for strings). Column names are sanitized for SQL compatibility.

Q: Which SQL dialect is the output compatible with?

A: The generated SQL uses standard ANSI SQL syntax, which is compatible with MySQL, PostgreSQL, SQLite, Microsoft SQL Server, Oracle, and most other relational database systems. The output avoids dialect-specific features to ensure maximum portability across different database engines.

Q: What happens to Markdown content that is not a table?

A: Non-table Markdown content (headings, paragraphs, lists, code blocks) is converted to SQL comments using the -- prefix. This preserves the documentation context alongside the SQL statements. Headings become section comments, and descriptive text is included as multi-line comments.

Q: Are string values properly escaped in the SQL output?

A: Yes, all string values are properly escaped using single quotes with special characters handled according to SQL standards. Single quotes within values are escaped as double single quotes (''). This ensures the generated SQL is safe to execute and prevents syntax errors or SQL injection issues.

Q: Can I convert multiple Markdown tables to separate SQL tables?

A: Yes! If your Markdown file contains multiple tables, each one is converted to a separate CREATE TABLE and corresponding INSERT statements. The table names are derived from the heading above each Markdown table, or auto-generated if no heading is present.

Q: How are data types determined for SQL columns?

A: The converter analyzes all values in each column to infer the most appropriate SQL type. Columns containing only integers become INTEGER, decimal numbers become DECIMAL, and everything else defaults to VARCHAR(255). Date-like values may be detected as DATE type depending on the format.

Q: Can I use the SQL output for database migrations?

A: Yes, the generated SQL can be used as migration scripts. You can execute them directly in your database client, include them in migration frameworks like Flyway or Liquibase, or use them as seed data scripts. The output includes both schema creation (CREATE TABLE) and data insertion (INSERT) statements.

Q: What if my Markdown doesn't contain tables?

A: If the Markdown file has no tables, the converter will output the entire content as SQL comments, preserving the text for reference. For best results, ensure your Markdown contains properly formatted GFM (GitHub Flavored Markdown) tables with headers, separator rows, and data rows.