Skip to main content

MySQL Core

MySQL Core is a connector dedicated to forks of MySQL, which are incompatible with our MySQL Connector. It provides almost all functionalities of MySQL Connector, however, it has some limitations.

Catalog and documentation

Data Dictionary

Dataedo imports tables, views, and their columns.

Stored procedures and functions

Stored procedures and user-defined functions will be imported with their parameters and code.

Descriptions, aliases, and custom fields

When technical metadata is imported, users will be able to edit descriptions of each object and element, provide meaningful aliases (titles), and document everything with additional custom fields.

Import and export comments

When importing metadata from MySQL, Dataedo reads table, view, and column comments (see specification below). Dataedo does not write comments back to MySQL.

Business Glossary

Users will be able to link a Business Glossary term to any MySQL Core object.

Table relationships and keys

Dataedo imports table relationships (foreign keys), primary and unique keys with their columns.

ER Diagrams

Using imported and manually created foreign keys, Dataedo builds ER diagrams (ERDs) automatically and allows you to create your own manually.

ER Diagrams

Data Profiling

MySQL Core currently does not support Data Profiling.

Lookups / Reference data

Users will be able to build Lookups for columns in Snowflake tables and views and feed them with distinct values from a column.

Data Classification

Users will be able to run classification) on MySQL Core database in the repository in search of columns containing potentially sensitive data. All built-in functions) are supported.

Data Classification

Importing changes and schema change tracking

To import changes from MySQL Core database and update metadata in Dataedo, simply use the Import changes option. Changes in the schema are tracked and displayed in the Schema changes tab.

Description changes

Changes to descriptions in Dataedo Desktop and Web Catalog are tracked and saved in the repository. They are not displayed in the Schema changes tab.

Design and generate schema

You will be able to design new tables and columns for your MySQL Core database.

Connecting to MySQL Core

To connect to MySQL Core, create new documentation by clicking Add documentation and choosing Database connection.

Connecting to MySQL Core

On the connection screen, choose MySQL Core as DBMS.

Provide database connection details:

  • Host - provide a host name or address where a database is on. E.g. server17, localhost, or 192.168.0.37.
  • Port - change the default port of MySQL instance if required
  • User and password - provide your username and password
  • Database - type in schema name
Image title

Importing changes

To sync any changes in the schema in MySQL Core and reimport any technical metadata, simply choose the Import changes option. You will be asked to connect to MySQL Core again and changes will be synced from the source.

Specification

Imported metadata

ImportedEditable
Tables
  Columns
   Data types
   Nullability
   Column comments
  Table comments
  Foreign keys
  Primary keys
  Unique keys
Views
  Script
  Columns
   Data types
   Column comments
  View comments
Stored procedures
  Script
  Parameters
User-defined Functions
  Script
  Input arguments (all as a single field)
  Output results (as a single field)
  Function comments

Supported features

FeatureImported
Import comments
Write comments back
Data profiling
Reference data (import lookups)
Importing from DDL
Generating DDL
FK relationship tester

Comments

Dataedo reads comments from the following MySQL Core objects:

ObjectReadWrite back
Table comments
  Column comments
View comments
  Columns
Function comments

Data profiling

Dataedo does not support data profiling in MySQL Core.

Data Lineage

SourceMethodVersion
Views - object levelFrom SQL parsing23.2 (2023)
Views - column levelFrom SQL parsing23.2 (2023)

Under development

Known issues and limitations

  • MySQL Core will not document: parameters and relations
  • Automatic lineage will only build between tables and views