CSV to SQL

Generated 2 SQL statement(s) for 2 row(s) across 2 column(s).

How it works

• Parsed the delimited text per RFC 4180 and sanitised the table/column identifiers.
• Inferred each column's SQL type conservatively for the optional CREATE TABLE.
• Quoted identifiers and escaped strings per the chosen dialect, then batched the INSERTs.

• A cell equal to the configured NULL token becomes an unquoted NULL; every other value is quoted as a string.

Methodology

1. Parse per RFC 4180 and sanitise the table and column identifiers to conservative tokens.
2. Infer each column's SQL type (integer/number/boolean/date/text) for the optional CREATE TABLE.
3. Quote identifiers and escape string literals per dialect (doubled quotes for standard/PostgreSQL/SQLite, backslash escaping and backtick identifiers for MySQL), then batch INSERTs.

Usage

1. Paste delimited text or choose a local file.
2. Choose the SQL dialect, table name, batch size and NULL token.
3. Optionally include a CREATE TABLE, then copy or download the statements.

Examples

These are examples, not current values: they use fixed inputs, while the interactive tool computes live results in your browser.

Generate PostgreSQL INSERTs

{
  "text": "id,name\n1,Ada\n2,Alan",
  "delimiterMode": "comma",
  "delimiter": ",",
  "firstRowHeader": true,
  "dialect": "postgresql",
  "tableName": "people",
  "batchSize": 2,
  "nullToken": "NULL",
  "createTable": true,
  "quoteIdentifiers": true
}

Limitations

Safety first

INSERT statements modify data. Inspect the generated SQL, check the table and column names and take a backup before running anything against a real database.

Dialect-aware quoting

Identifiers and string literals are quoted per the selected dialect so a column named with a space, or a value containing an apostrophe, does not break the statement.