<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Advanced data tools :: DbGate</title>
    <link>https://dbgate.io/dbgate-classic/working-with-data/advanced-data-tools/index.html</link>
    <description>DbGate offers several advanced data tools suitable for specific scenarios:&#xA;Data archives - table data stored in folders (on NDJSON format) on your local computer. You could browse and edit this data in the similar way as browsing tables in database Data deployer - visually compare and synchronize data between data archive and real database Data replicator - replicate your data from data archive to database, suitable for run from DbGate app or from command line</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <atom:link href="https://dbgate.io/dbgate-classic/working-with-data/advanced-data-tools/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Data archives</title>
      <link>https://dbgate.io/dbgate-classic/working-with-data/advanced-data-tools/archives/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://dbgate.io/dbgate-classic/working-with-data/advanced-data-tools/archives/index.html</guid>
      <description>Archives are folders with data in JSONL (NDJSON) format. DbGate allows work with them very efficiently, you could import them into database, export them to other formats or directly edit data in archive. Archive behaves as a very fast and lighweight database stored in local files.&#xA;JSONL format DbGate uses JSONL format internally everywhere. JSONL is text file, where every line contains JSON stringified row. DbGate assumes, that first line could contain header (also as JSON), with table structure. When you use JSONL with dynamic structure (without first fixed line), this format is standardized and could be loaded into many other tools.</description>
    </item>
    <item>
      <title>Data deployer</title>
      <link>https://dbgate.io/dbgate-classic/working-with-data/advanced-data-tools/data-deployer/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://dbgate.io/dbgate-classic/working-with-data/advanced-data-tools/data-deployer/index.html</guid>
      <description>With data deployer, you could visually compare and sycnhronize your data in archive folders with real database Run data deployer You could run data deployer from database context menu or from archive folder context menu. When running archive database, you will be asked to choose archive. When running from archive, data deployer will be started with current database.</description>
    </item>
    <item>
      <title>Data replicator</title>
      <link>https://dbgate.io/dbgate-classic/working-with-data/advanced-data-tools/data-replicator/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://dbgate.io/dbgate-classic/working-with-data/advanced-data-tools/data-replicator/index.html</guid>
      <description>Data replicator could synchronize your data in NDJSON files (data archives) with real database. It preserves relationships. Synchronization is one-way, from data archive data into database.&#xA;Data replicator is executed from Data deployer&#xA;What means to preserve relationship? References are defined by foreign and primary keys. These values could be different in database and in archive, but replicator could preserve relationships between entities.&#xA;We will show this on two related tables - Album and Track.</description>
    </item>
  </channel>
</rss>