My account Book a demo

PostgreSQL Parsing

Hubert Książek - Dataedo Team Hubert Książek 4th May, 2023
Applies to: Dataedo 23.x versions, Article available also for: 24.x (current)
You are looking at documentation for an older release.
Switch to the documentation for Dataedo 24.x (current).

In this document, you will be able to see where Dataedo uses an SQL parser that uses the PostgreSQL dialect and what its capabilities are.

What is an SQL Parser?

A SQL parser is a tool that reads SQL code and converts it into a format that can be understood and processed by a computer. The parser is an important component of any metadata management system like Dataedo as it allows them to analyze SQL queries and fetch the relevant metadata.

Click to learn more about the other parser features.

Supported engines

Engines that use this dialect:

Import schema from DDL

Data Definition Language (DDL) is a subset of SQL that is used to describe database structure and relationships in a database. With the help of an SQL Parser, Dataedo imports the schema based on the given DDL. Read more.

Import metadata from DDL

This feature is also available for T-SQL dialect.

Automatic column-level lineage from SELECT/CREATE VIEW statements

Dataedo will create column-level data lineage for views and SQL queries based on the script. Just leave the "Automatic lineage" option selected during import.

How to enable automatic data lineage from Dataedo during import

If you disable the this feature during import, you will still be able to trigger the automated creation of column-level lineage through the "Parse Script to Lineage" functionality, which is located in the Script tab.

How to enable automatic data lineage from Dataedo after import using Parse script to lineage

This function also works for manually added views that was created using a script, as well as for SQL Query objects.

Supported SQL syntax

We support the creation of an automatic lineage in all dialects for the following SQL syntax:

  • SELECT and CREATE VIEW statements,
  • Aliases,
  • Functions and operators,
  • UNIONs,
  • JOINs,
  • Subqueries and nested queries,
  • CASEs and other logic-related expressions,
  • Not Recursive Common Table Expressions (CTE).

We do not support the creation of an automatic lineage for the following SQL syntax:

  • Statements that access nested data such JSON, XML, or objects as columns
  • PIVOT and UNPIVOT relational operators,
  • Recursive Common Table Expressions (Recursive CTE),
  • Dynamic queries,
  • Window functions,
  • Statments that uses asterisk (*).
Contact support Report issue