JSON-Studio/sql.html at main · jssuthahar/JSON-Studio · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<title>JSON to SQL — CREATE TABLE and INSERT for Postgres, MySQL, SQL Server | JSON Studio</title>
<meta name="description" content="Turn a JSON array into CREATE TABLE and INSERT statements for PostgreSQL, MySQL, SQL Server or SQLite, with column types inferred across every row. Free, client-side, no upload.">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<link rel="canonical" href="https://jsonstudio.msdevbuild.com/sql.html">
<link rel="manifest" href="manifest.webmanifest">
<meta name="theme-color" content="#0078d4" media="(prefers-color-scheme: light)">
<meta name="theme-color" content="#12151c" media="(prefers-color-scheme: dark)">
<link rel="apple-touch-icon" href="assets/img/apple-touch-icon.png">
<meta name="apple-mobile-web-app-capable" content="yes">
<meta name="apple-mobile-web-app-title" content="JSON Studio">
<link rel="icon" href="assets/img/favicon.svg" type="image/svg+xml">

<meta property="og:type" content="website">
<meta property="og:title" content="JSON to SQL — CREATE TABLE and INSERT for Postgres, MySQL, SQL Server">
<meta property="og:description" content="Turn a JSON array into CREATE TABLE and INSERT statements for PostgreSQL, MySQL, SQL Server or SQLite, with column types inferred across every row. Free, client-side, no upload.">
<meta property="og:url" content="https://jsonstudio.msdevbuild.com/sql.html">
<meta property="og:image" content="https://jsonstudio.msdevbuild.com/assets/img/og-cover.png">
<meta property="og:image:width" content="1200">
<meta property="og:image:height" content="630">
<meta property="og:image:alt" content="JSON Studio — every JSON tool, in your browser">
<meta property="og:site_name" content="JSON Studio by MSDEVBUILD">

<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:image" content="https://jsonstudio.msdevbuild.com/assets/img/og-cover.png">
<meta name="twitter:title" content="JSON to SQL — CREATE TABLE and INSERT for Postgres, MySQL, SQL Server">
<meta name="twitter:description" content="Turn a JSON array into CREATE TABLE and INSERT statements for PostgreSQL, MySQL, SQL Server or SQLite, with column types inferred across every row. Free, client-side, no upload.">

<link href="https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700&family=JetBrains+Mono:wght@400;500;700&display=swap" rel="stylesheet">
<link rel="stylesheet" href="assets/css/styles.css">
<link rel="stylesheet" href="assets/css/convert.css">
<link rel="stylesheet" href="assets/css/present.css">
<link rel="stylesheet" href="assets/css/workbench.css">
<link rel="stylesheet" href="assets/css/tool-focus.css">
<link rel="stylesheet" href="assets/css/editor.css">

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "SoftwareApplication",
  "name": "JSON to SQL — CREATE TABLE and INSERT generator — JSON Studio",
  "url": "https://jsonstudio.msdevbuild.com/sql.html",
  "applicationCategory": "DeveloperApplication",
  "operatingSystem": "Any (runs in browser)",
  "offers": { "@type": "Offer", "price": "0", "priceCurrency": "USD" },
  "creator": { "@type": "Person", "name": "Suthahar Jegatheesan", "url": "https://www.msdevbuild.com/" },
  "description": "Turn a JSON array into CREATE TABLE and INSERT statements for PostgreSQL, MySQL, SQL Server or SQLite. Free, client-side."
}
</script>
<script>(function(){try{var t=localStorage.getItem('json-studio-theme');if(!t&&window.matchMedia&&matchMedia('(prefers-color-scheme: dark)').matches)t='dark';if(t)document.documentElement.setAttribute('data-theme',t);}catch(e){}})();</script>
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "BreadcrumbList",
      "itemListElement": [
        { "@type": "ListItem", "position": 1, "name": "JSON Studio", "item": "https://jsonstudio.msdevbuild.com/" },
        { "@type": "ListItem", "position": 2, "name": "Tools", "item": "https://jsonstudio.msdevbuild.com/tools.html" },
        { "@type": "ListItem", "position": 3, "name": "JSON to SQL", "item": "https://jsonstudio.msdevbuild.com/sql.html" }
      ]
    },
    {
      "@type": "FAQPage",
      "mainEntity": [
        { "@type": "Question", "name": "Which databases are supported?", "acceptedAnswer": { "@type": "Answer", "text": "PostgreSQL, MySQL, SQL Server and SQLite. Identifier quoting, boolean literals and type names follow each dialect — JSONB for Postgres, JSON for MySQL, NVARCHAR(MAX) for SQL Server, TEXT for SQLite." } },
        { "@type": "Question", "name": "What happens to nested objects and arrays?", "acceptedAnswer": { "@type": "Answer", "text": "They are stored as JSON text in a single column, which is what all four databases would have you do anyway. Flatten them first with the CSV tool if you want separate columns." } },
        { "@type": "Question", "name": "Is the generated SQL safe to run?", "acceptedAnswer": { "@type": "Answer", "text": "Values are inlined as escaped literals, which is fine for seeding and fixtures. Do not build a pipeline that inlines untrusted input this way — use parameterised queries for anything user-driven." } }
      ]
    },
    {
      "@type": "HowTo",
      "name": "How to use the JSON to SQL",
      "step": [
        { "@type": "HowToStep", "position": 1, "text": "Paste an array of JSON objects." },
        { "@type": "HowToStep", "position": 2, "text": "Pick the dialect and table name, and whether columns are converted to snake_case." },
        { "@type": "HowToStep", "position": 3, "text": "Copy the SQL, or download it as a .sql file." }
      ]
    }
  ]
}
</script>
</head>
<body>

<div id="site-header"></div>
<span id="top"></span>

<main class="convert-shell">
  <div class="convert-head">
    <div class="container tool-topbar">
      <h1>JSON to SQL</h1>
      <p class="tt-sub">CREATE TABLE and INSERT statements for Postgres, MySQL, SQL Server or SQLite.</p>
      <a class="tt-about" href="#about">About &amp; FAQ ↓</a>
    </div>
    <div class="container">
      <div class="opt-bar">
        <div class="opt">
          <label for="opt-dialect">Dialect</label>
          <select id="opt-dialect">
            <option value="postgres" selected>PostgreSQL</option>
            <option value="mysql">MySQL</option>
            <option value="mssql">SQL Server</option>
            <option value="sqlite">SQLite</option>
          </select>
        </div>
        <div class="opt">
          <label for="opt-table">Table</label>
          <input type="text" id="opt-table" value="my_table" style="min-width:120px;">
        </div>
        <div class="opt-sep"></div>
        <div class="opt">
          <input type="checkbox" id="opt-create" checked>
          <label for="opt-create" style="cursor:pointer;">CREATE TABLE</label>
        </div>
        <div class="opt">
          <input type="checkbox" id="opt-multi" checked>
          <label for="opt-multi" style="cursor:pointer;">Multi-row INSERT</label>
        </div>
        <div class="opt">
          <input type="checkbox" id="opt-snake" checked>
          <label for="opt-snake" style="cursor:pointer;">snake_case columns</label>
        </div>
      </div>
    </div>
  </div>
  <div class="convert-grid">
    <section class="pane">
      <div class="pane-head">
        <div class="pane-title">JSON array</div>
        <button id="btn-sample">Load sample</button>
        <button id="btn-upload">Upload</button>
        <button id="btn-clear">Clear</button>
        <input type="file" id="file-input" accept=".json,application/json" style="display:none;">
      </div>
      <div class="pane-body">
        <textarea id="input" class="code-area" spellcheck="false" placeholder="[{"id": 1, "name": "Ada"}]"></textarea>
      </div>
      <div class="pane-status" id="in-status">Waiting for input.</div>
    </section>

    <section class="pane">
      <div class="pane-head">
        <div class="pane-title">SQL</div>
        <button class="primary" id="btn-run">Generate</button>
        <button id="btn-copy">Copy</button>
        <button id="btn-download">Download</button>
      </div>
      <div class="pane-body">
        <textarea id="output" class="code-area" spellcheck="false" readonly placeholder="Generated SQL appears here."></textarea>
        <p class="note">Values are inlined as literals with quotes escaped — fine for seeding and fixtures, but use parameterised queries for anything driven by untrusted input.</p>
      </div>
      <div class="pane-status" id="out-status"></div>
    </section>
  </div>
</main>


<section class="tool-home" id="about">
  <div class="container">
    <div class="th-more">Reference</div>
    <header class="th-head">
      <div class="kicker">JSON to SQL</div>
      <h2>About the JSON to SQL generator</h2>
      <p>Getting a JSON export into a database usually means writing the DDL by hand. This infers column types from every row rather than the first — a column holding 1, 2 and 3.5 becomes decimal, and a column that is ever missing or null becomes nullable — then emits a CREATE TABLE and the INSERT statements to load it, quoted correctly for your dialect.</p>
      <div class="cta-row">
        <a class="btn-primary" href="#top">Use the tool ↑</a>
        <a class="btn-secondary btn-present" href="presentation.html"><svg class="nav-ico" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="1.7" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><rect x="3" y="4" width="18" height="13" rx="2"/><path d="M12 17v3M9.5 20h5"/><path d="m10.6 8.8 4 2.7-4 2.7z" fill="currentColor" stroke="none"/></svg> Present it</a>
      </div>
    </header>

    <div class="th-features">
      <div class="th-feature">
        <div class="fi">01</div>
        <h3>Four dialects</h3>
        <p>PostgreSQL, MySQL, SQL Server and SQLite, each with correct quoting, types and boolean literals.</p>
      </div>
      <div class="th-feature">
        <div class="fi">02</div>
        <h3>Types from every row</h3>
        <p>A column holding 1, 2 and 3.5 becomes decimal; a column ever missing becomes nullable.</p>
      </div>
      <div class="th-feature">
        <div class="fi">03</div>
        <h3>CREATE plus INSERT</h3>
        <p>Table definition and the statements to load it, chunked for large sets.</p>
      </div>
      <div class="th-feature">
        <div class="fi">04</div>
        <h3>Nested data handled</h3>
        <p>Objects and arrays are stored as JSON text columns, which is what these databases want anyway.</p>
      </div>
    </div>

    <div class="seo-grid">
      <div class="seo-main">
        <h3 id="how">How to use it</h3>
        <ol class="seo-steps">
          <li>Paste an array of JSON objects.</li>
          <li>Pick the dialect and table name, and whether columns are converted to snake_case.</li>
          <li>Copy the SQL, or download it as a .sql file.</li>
        </ol>

        <h3 id="faq">Questions</h3>
        <div class="faq">
          <details>
            <summary>Which databases are supported?</summary>
            <div class="faq-body"><p>PostgreSQL, MySQL, SQL Server and SQLite. Identifier quoting, boolean literals and type names follow each dialect — JSONB for Postgres, JSON for MySQL, NVARCHAR(MAX) for SQL Server, TEXT for SQLite.</p></div>
          </details>
          <details>
            <summary>What happens to nested objects and arrays?</summary>
            <div class="faq-body"><p>They are stored as JSON text in a single column, which is what all four databases would have you do anyway. Flatten them first with the CSV tool if you want separate columns.</p></div>
          </details>
          <details>
            <summary>Is the generated SQL safe to run?</summary>
            <div class="faq-body"><p>Values are inlined as escaped literals, which is fine for seeding and fixtures. Do not build a pipeline that inlines untrusted input this way — use parameterised queries for anything user-driven.</p></div>
          </details>
        </div>
      </div>

      <aside class="seo-side">
        <div class="seo-card" id="share">
          <h3>Share this tool</h3>
          <p>Send it to a colleague — the link only, never anything you have pasted in.</p>
          <div data-share data-share-title="JSON to SQL — JSON Studio"></div>
        </div>
        <div class="seo-card">
          <h3 class="with-ico"><svg class="nav-ico" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="1.7" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><rect x="3" y="4" width="18" height="13" rx="2"/><path d="M12 17v3M9.5 20h5"/><path d="m10.6 8.8 4 2.7-4 2.7z" fill="currentColor" stroke="none"/></svg> Present this tool</h3>
          <p>Demoing to a client or a class? Press <kbd>Shift</kbd><kbd>P</kbd> for full-screen presentation mode — chrome hidden, type scaled up, laser pointer included.</p>
          <a class="seo-link" href="presentation.html">How presentation mode works →</a>
        </div>
        <div class="seo-card">
          <h3>Related tools</h3>
          <ul class="seo-related">
            <li><a href="csv.html"><span class="ri">J↔C</span>JSON ⇄ CSV</a></li>
            <li><a href="jsonl.html"><span class="ri">≡</span>JSONL ⇄ JSON</a></li>
            <li><a href="code.html"><span class="ri"></></span>JSON to code</a></li>
          </ul>
          <a class="seo-link" href="tools.html">All 14 tools →</a>
        </div>
        <div class="seo-card quiet">
          <h3>Private by construction</h3>
          <p>No backend exists. Everything on this page runs in your browser, so nothing you paste is uploaded, logged or retained.</p>
          <a class="seo-link" href="privacy.html">Read the privacy policy →</a>
        </div>
      </aside>
    </div>
  </div>
</section>

<div id="site-footer"></div>

<script src="assets/js/site.js"></script>
<script src="assets/js/payload-link.js"></script>
<script src="assets/js/tool-kit.js"></script>
<script src="assets/js/sql.js"></script>
<script src="assets/js/present.js"></script>
<script src="assets/js/workbench.js"></script>
<script src="assets/js/history.js"></script>
<script src="assets/js/gutter.js"></script>
<script src="assets/js/editor.js"></script>
<script src="assets/js/share.js"></script>
</body>
</html>