dbd 0.5.5

Framework for declarative database creation and management.

DBD - framework for declarative database definition

DBD framework allows you to define your database schema and content declaratively. Database is represented by a hierarchy of directories and files stored in your DBD project files.

TLDR: Whetting Your Appetite

1. dbd init test
2. cd test
3. dbd validate .
4. dbd run .
5. Connect to the newly created states.db database and review area, population, and state tables that have been created from the files in the model directory.

Now you can delete the example files from the model directory, copy your Excel, JSON, or CSV files there instead. Then execute dbd run . again. Your files should get loaded into the database.

You can create a YAML configuration files for your Excel, JSON, or CSV files to specify individual column's data types, indexes or constraints (e.g. primary key, foreign key, or check). See below for more details.

Then you can also create an SQL file that performs SQL insert-from-select to transform the loaded data.

Install DBD

DBD requires Python 3.7.1 or higher.

PyPI

pip3 install dbd

OR

git clone https://github.com/zsvoboda/dbd.git
cd dbd
pip3 install .

Poetry

git clone https://github.com/zsvoboda/dbd.git
cd dbd
poetry install

Generate a new DBD project

You can generate initial layout of your DBD project using the init command:

dbd init <new-project-name>

The init command generates a new DBD project directory with the following content:

• model directory that contains the content files. dbd supports files with .sql, .ddl, .csv, .json, .xlsx and other extensions.
• dbd.project project configuration file

DBD also requires dbd.profile configuration file that contains connections to your databases. This file is located in the current directory or in your home directory.

DBD profile configuration file

DBD stores database connections in a profile configuration file. It searches for dbd.profile file in the current or in your home directory. You can always specify a custom profile file location using the --profile option of the dbd command.

The profile file is YAML file with the following structure:

databases:
  states:
    db.url: <sql-alchemy-database-url>

Read more about SQL Alchemy database URLs here.

The profile file can contain Jinja2 macros that substitute your environment variables. For example, you can reference database password stored in a $SQLITE_PASSWORD environment variable via {{ SQLITE_PASSWORD }} in your DBD profile.

DBD project configuration file

DBD stores project configuration in a project configuration file that is usually stored in your DBD project directory. DBD searches for dbd.project file in the current directory. You can also use the --project option pf the dbd command to specify a custom project configuration file.

The project configuration file also uses YAML format and references the DBD model directory with the .sql, .csv and other supported files. It also references the database configuration from the profile config file. For example:

model: model
database: states

Similarly like the profile file, you can use the environment variables substitution in the procet config file too (e.g. {{ SQLITE_DB_NAME }}).

Model directory

The model directory contains directories and DBD files. Each subdirectory of the model directory represents a database schema. For example, this model directory structure

dbd-project-directory
+- schema1
 +-- us_states.csv
+- schema2
 +-- us_counties.csv

creates two database schemas: schema1 and schema2 and creates two database tables: us_states in schema1 and us_counties in schema2. Both tables are populated with the data from the CSV files.

The following file types are supported:

• DATA files: .csv, .json, .xls, .xlsx, .parquet files are loaded to the database as tables
• SQL files: with SQL SELECT statements are executed using insert-from-select SQL construct. The INSERT command is generated (the SQL file only contains the SQL SELECT statement)
• DDL files: contain a sequence of SQL statements separated by semicolon. The DDL files can be named prolog.ddl and epilog.ddl. The prolog.ddl is executed before all other files in a specific schema. The epilog.ddl is executed last. The prolog.ddl and epilog.ddl in the top-level model directory are executed as the very first and tne very last files in the model.
• YAML files: specify additional configuration to the DATA and SQL files.

YAML model files

YAML file specify additional configuration for a corresponding DATA or SQL file with the same base file name. here is an area.csv YAML configuration example:

table:
  columns:
    state_name:
      nullable: false
      index: true
      primary_key: true
      foreign_keys:
        - state.state_name
      type: VARCHAR(50)
    area_sq_mi:
      nullable: false
      index: true
      type: INTEGER
process:
  materialization: table
  mode: drop

Process section

The process section specifies the following processing options:

• materialization: specifies whether DBD creates a physical table or a view when processing a SQL file.
• mode: specifies how DBD works with a table. You can specify values drop, truncate, or keep. The mode option is ignored for views.

Table section

YAML file's columns are mapped to the area.csv data file columns by the column name. The following column parameters are supported:

• type: column's SQL type.
• primary_key: is the column part of table's primary key (true|false)?
• foreign_keys: all other database table columns that are referenced from a column in . format
• nullable: does column allow null values (true|false)?
• index: is column indexed (true|false)?
• unique: does column store unique values (true|false)?