Input
π‘ Add a JSON array or object below. Types are detected automatically.
All processing happens locally in your browser β no data is sent anywhere.
π Schema: PostgreSQL uses a schema, MySQL uses a database, SQLite has no schema.
π° Fields named
β οΈ Generated code is provided "as is". Always verify generated SQL before running on production databases. Read our Terms of Service.
All processing happens locally in your browser β no data is sent anywhere.
π Schema: PostgreSQL uses a schema, MySQL uses a database, SQLite has no schema.
π° Fields named
price, cena, iznos, vrednost, quantity, kolicina, amount, total, cost, tezina, procenat, popust, discount, percentage, tax, vat, pdv, percent (or variants like unit_price) default to NUMERIC(16,2) even when the values are whole numbers.
β οΈ Generated code is provided "as is". Always verify generated SQL before running on production databases. Read our Terms of Service.
Normalized (masterβdetail): nested 1:1 objects are flattened into prefixed columns (see Depth below); every array of objects becomes a detail table with an
Path escaping (so a key character can't collide with the path structure):
<parent>_id foreign key, recursively (master β detail β detailβ¦). Objects deeper than Depth are stored as JSON.
Path mode stores one row per JSON node (path, key_name, type, val) β best for unknown or irregular JSON.Path escaping (so a key character can't collide with the path structure):
~ β ~0, . β ~1,
[ β ~2, ] β ~3.
E.g. key a.b becomes path segment a~1b, while nested
a β b stays a.b.
How many levels of nested 1:1 objects to flatten into prefixed columns. 0 = no flattening (objects stay JSON); 1 =
a_x; 2 = a_b_x; etc. Arrays of objects always become detail tables, regardless of this value. (Default 2 = the previous behaviour.)
SQL Result
β
Generated SQL code appears here