Documentation

gitHub

MariaDB

MariaDB is a community-developed, commercially supported fork of the MySQL relational database management system, intended to remain free and open-source software.  In addition to high compatibility with MySQL, it provides support for multiple different storage engines designed to efficiently manage data files, the data, and the index caches.

 

With version 10, MariaDB introduced JSON functions to combine NoSQL and relational concepts in the same database. Users can combine classic relational columns with columns that contain documents formatted as JSON text in the same table, parse and import JSON documents in relational structures, or format relational data to JSON text.

 

To perform data modeling for MariaDB with Hackolade, you must first download the MariaDB plugin.  

 

Hackolade was specially adapted to support the data modeling of MariaDB, including databases, tables and views, indexes and constraints, plus the generation of DDL Create Table syntax. 

 

In particular, Hackolade has the unique ability to model complex semi-structured objects stored in columns of the LONGTEXT columns.  We're not talking about functions that "flatten" JSON into standard columns, which runs the risk of inconsistencies, if not errors, when doing the Cartesian product of multiple complex data types.  But about the storage of entire JSON documents.  The reverse-engineering function, if it detects JSON documents, will sample records and infer the schema to supplement the DDL table definitions.  

 

The data model in the picture below results from the data modeling of the Sakila sample database:

 

Image

 

Databases

MariaDB tables are contained within database object containers.  The database also works as a security boundary, where you can limit database user permissions to be on a specific schema level only.  

 

Database engines

Storage engines handle data at the physical level. Storage engines are designed to efficiently manage data files, the data, and the index caches.

 

Tables

All data in MariaDB is stored in database tables, logically structured as collections of columns and rows, optionally with single-column or multi-column constraints.  

 

Unique, Primary, and Foreign Keys, plus Not Null, Check and Default constraints

Constraints in MariaBD are predefined rules and restrictions that are enforced in a single column or multiple columns, regarding the values allowed in the columns, to maintain the integrity, accuracy, and reliability of that column’s data. Constraints in MariaDB can be defined at the column level, where it is specified as part of the column definition and will be applied to that column only, or declared independently at the table level. 

 

There are six main constraints that are commonly used in MariaDB: NOT NULL, UNIQUE, PRIMARY, FOREIGN, CHECK, and DEFAULT.  

Indexes

The goal of an index on a database table then is to reduce I/O.  Properly indexing a MariaDB table is key to providing consistent, optimal performance. There are many things to consider when designing an index structure, but this goes beyond the scope of this document.  

 

Hackolade supports the most common types of MariaDB indexes, but not all of them yet.  

 

Data types

In MariaDB, each column, local variable, expression, and parameter has a related data type. A data type is an attribute that specifies the type of data that the object can hold: integer data, character data, monetary data, date and time data, binary strings, and so on.

 

Additionally, in LONGTEXT columns, Hackolade supports the data modeling of JSON files with standard JSON data types: string, number, object, array, boolean, and null.

 

User-defined data types are based on the data types in MariaDB. User-defined data types can be used when several tables store the same domain of values in a column and must ensure that these columns have exactly the same data type, length, and NULLability.

 

Views

A view is a virtual table whose contents are defined by a query. Like a table, a view consists of a set of named columns and rows of data. Unless indexed, a view does not exist as a stored set of data values in a database. The rows and columns of data come from tables referenced in the query defining the view and are produced dynamically when the view is referenced.  A view acts as a filter on the underlying tables referenced in the view. The query that defines the view can be from one or more tables or from other views in the current or other databases.

 

Functions and Procedures

A function takes any number of arguments and returns a value from the function body. The function body can be any valid SQL expression as you would use, for example, in any select expression.A Stored Procedure is a routine invoked with a CALL statement. It may have input parameters, output parameters and parameters that are both input parameters and output parameters.

 

Forward-Engineering

Hackolade dynamically generates the DDL script to create databases, tables, columns and their data types, indexes and constraints for the structure created with the application, as well as functions and procedures.

 

Image

 

If you store JSON within LONGTEXT columns, Hackolade allows for the schema design of those documents.  However, the corresponding JSON structure is not forward-engineered in the DDL script, but is useful for developers, analysts and designers.

 

Reverse-Engineering

The MariaDB engine can hosted on-premises, or on virtualized machines in a private or public cloud Details on how to connect Hackolade to MariaDB can be found on this page.

 

The Hackolade process for reverse-engineering of MariaDB databases includes the execution of statements to discover databases, tables, columns and their types, indexes and constraints.  If JSON is detected in LONGTEXT columns, Hackolade performs statistical sampling of records followed by probabilistic inference of the JSON document schema.

 

For more information on MariaDB in general, please consult the website and documentation.