<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Keto Man</title>
    <description>The latest articles on DEV Community by Keto Man (@ketoman).</description>
    <link>https://dev.to/ketoman</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3244644%2F033ce1ac-a656-4bee-b27e-3400960a8c6b.png</url>
      <title>DEV Community: Keto Man</title>
      <link>https://dev.to/ketoman</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/ketoman"/>
    <language>en</language>
    <item>
      <title>From JSONL to a normalized relational database. Is a tool necessary?</title>
      <dc:creator>Keto Man</dc:creator>
      <pubDate>Fri, 11 Jul 2025 13:36:51 +0000</pubDate>
      <link>https://dev.to/ketoman/from-jsonl-to-a-normalized-relational-database-is-a-tool-necessary-4i7j</link>
      <guid>https://dev.to/ketoman/from-jsonl-to-a-normalized-relational-database-is-a-tool-necessary-4i7j</guid>
      <description>&lt;p&gt;This is my first post, please forgive me if it’s not the most beautiful post you’ll read. 😃&lt;/p&gt;

&lt;p&gt;In my career as a developer, I often find myself spending a lot of time on the lengthy and resource-intensive task of extracting data from JSON files and placing them into relational databases so that data querying for analysts and others is facilitated by the use of SQL.&lt;/p&gt;

&lt;p&gt;These are very time-consuming activities with a fairly high risk of making errors if not handled correctly.&lt;/p&gt;

&lt;p&gt;For this reason, I have created a tool that automatically performs this task.🥳&lt;/p&gt;

&lt;p&gt;What does this tool consist of?&lt;br&gt;
In practice, JSONs are saved as JSONL within a text file.&lt;br&gt;
Each individual line is analyzed to understand the structure of all the JSON paths within them.&lt;br&gt;
Once this analysis is complete, a script creates the necessary structures for a PostgreSQL database (and soon for Oracle, Snowflake, etc.).&lt;/p&gt;

&lt;p&gt;The result is an SQL script to be executed on the database, providing ready-to-use structures for the JSON data.&lt;/p&gt;

&lt;p&gt;I have saved countless hours compared to before, and above all, if I receive any JSON input today, I no longer have to worry about its structure or writing the linking keys between the various tables.&lt;/p&gt;

&lt;p&gt;You should know, in fact, that I have very complex JSONs, with up to 15 hierarchical levels, and... it works perfectly.&lt;/p&gt;

&lt;p&gt;The interesting aspect of this utility is that it also automatically adapts to changes. Any new branches or variations are automatically detected, maintaining backward compatibility with already loaded data. You just need to rerun the script if changes are reported.&lt;/p&gt;

&lt;p&gt;This utility also works if the input refers to XML!&lt;/p&gt;

&lt;p&gt;Now the question I have for you is this: is this utility only useful to me, or are there other developers who might find it necessary? Let me know because I'm curious. 😃&lt;/p&gt;

</description>
      <category>json</category>
      <category>database</category>
      <category>xml</category>
      <category>postgres</category>
    </item>
    <item>
      <title>Hello everyone. In your opinion, does it make sense to have a tool that automatically extracts data from JSON files, without first knowing the structure of the JSON schema, and transforms this data into a normalized relational database? How many of you mig</title>
      <dc:creator>Keto Man</dc:creator>
      <pubDate>Fri, 11 Jul 2025 13:08:00 +0000</pubDate>
      <link>https://dev.to/ketoman/hello-everyone-in-your-opinion-does-it-make-sense-to-have-a-tool-that-automatically-extracts-l57</link>
      <guid>https://dev.to/ketoman/hello-everyone-in-your-opinion-does-it-make-sense-to-have-a-tool-that-automatically-extracts-l57</guid>
      <description></description>
      <category>discuss</category>
      <category>database</category>
      <category>automation</category>
      <category>softwareengineering</category>
    </item>
  </channel>
</rss>
