Metadata-Version: 2.1
Name: pg-db-tools
Version: 1.0.3
Summary: PostgreSQL database schema design and maintenance tools
Home-page: http://www.hendrikx-itc.nl
Author: Alfred Blokland
Author-email: alfred.blokland@hendrikx-itc.nl
License: UNKNOWN
Platform: UNKNOWN
Requires-Dist: PyYAML
Requires-Dist: jsonschema
Requires-Dist: networkx
Requires-Dist: Jinja2
Requires-Dist: psycopg2-binary

PostgreSQL Database Tools
=========================

|Crates.io|

.. |Crates.io| image:: https://img.shields.io/pypi/v/pg-db-tools.svg
   :target: https://pypi.org/project/pg-db-tools/

Design, create, maintain and document a PostgreSQL databases using a yaml based
descriptions.

Read the `documentation on readthedocs.io <https://pg-db-tools.readthedocs.io/en/latest/>`_.

Installation
------------

Install from PyPi::

    $ pip3 install pg-db-tools


Install from GitHub::

    $ git clone https://github.com/hendrikx-itc/pg-db-tools
    $ sudo pip3 install pg-db-tools

Usage
-----

Command usage::

    db-schema <command> [options]

    commands:
        compile       compile output from schema definition
        extract       extract schema definition from source
        doc           documentation generation command
        --help,-h     display help information


compile
~~~~~~~

Sub-command compile::

    db-schema compile <output-type> <schema-filename>

    output-types:
        dot   Generate Graphviz DOT
        sql   Generate SQL
        md    Generate Markdown documentation
        rst   Generate reStructuresText documentation


extract
~~~~~~~

Sub-command extract::

    db-schema extract <source>

    sources:
        from-db   Extract from postgres database

Sub-sub-command from-db::

    db-schema extract from-db --format {yaml.json} [--owner OWNER] [schemas]

schemas:
* Multiple schemas can be supplied
* If no schema is supplied, all schemas are returned

Example::

    PGHOST=localhost \
    PGPORT=5432 \
    PGUSER=postgres \
    PGDATABASE=postgres \
    db-schema extract from-db --format yaml


doc
~~~


Examples
--------

Create sql from the example webshop.yaml::

    $ db-schema compile sql example/webshop.yaml

Create rst documentation from the example webshop.yaml::

    $ db-schema compile rst example/webshop.yaml


result::

    Schema ``shop``
    ===============


    Tables
    ------

    Order
    ^^^^^

    Contains all orders

    +---------+--------------------------+----------+-------------+
    | Column  | Type                     | Nullable | Description |
    +=========+==========================+==========+=============+
    | id      | integer                  | ✔        | Primary key |
    +---------+--------------------------+----------+-------------+
    | created | timestamp with time zone | ✔        |             |
    +---------+--------------------------+----------+-------------+

    OrderLine
    ^^^^^^^^^

    Contains all order lines for all orders

    +------------+---------+----------+-------------+
    | Column     | Type    | Nullable | Description |
    +============+=========+==========+=============+
    | id         | integer | ✔        | Primary key |
    +------------+---------+----------+-------------+
    | order_id   | integer | ✔        |             |
    +------------+---------+----------+-------------+
    | line_nr    | integer | ✔        |             |
    +------------+---------+----------+-------------+
    | product_id | integer | ✔        |             |
    +------------+---------+----------+-------------+
    | amount     | integer | ✔        |             |
    +------------+---------+----------+-------------+

    Schema ``public``
    =================


Description Format
------------------

One of the main components of the toolset is a database schema description
format. The description format is based on YAML, because it is easy to read and
write for humans.

See an example [here](https://github.com/hendrikx-itc/pg-db-tools/blob/master/example/webshop.yaml)

See the schema file [here](https://github.com/hendrikx-itc/pg-db-tools/blob/master/src/pg_db_tools/spec.schema)

Note
----

This tool is specifically not meant as a cross database toolset, because
that usually causes compatibility headaches and multiple partially supported
database engines.


