piotrkowalczuk / pqt

Postgres schema definition, sql/go, code generation package.

pqt  

This package is a toolbox for Postgres driven applications. It provides multiple tools to help to work with Postgres efficiently. In comparison to other currently available libraries instead of pushing struct tags into anti-pattern or parsing SQL, it allows defining schema programmatically.

From a developer perspective, pqt is primarily a toolkit generator, not an ORM. It means it is focusing on bringing low-level building blocks. Generated DAL (Data Access Layer) is only a (desired) side effect, a proof that those components fit together well.

A developer gets full access to the internals. Building your own, type-safe logic takes minutes. As a result, transition in and out is easy. No fear that you will be stuck with an ORM that doesn't meet your requirements anymore.

Documentation

• wiki
  • Features
  • Entities
  • Types
  • Repositories
  • Error Handling
• godoc
  • pqt
  • pqtgo
  • pqtsql

Example

The package itself does not provide any command line application that would generate output out of given input. Instead, it encourages to write local generation application next to the proper package. A good example of how such an application could be structured can be found in examples.

By default, the example is trying to connect to local test database on the default port. To run it simply call:

$ make gen // not necessary, since generated code is already part of the repo
$ make run

Plugins

pqtgo supports plugins over the interface.

• ntypespqt
• qtypespqt

Contribution

TODO

pqt's Issues

table aliases

I would suggest to introduce table aliases for using them in query.

Problem
E.g.: if we use column like this

pqt.NewColumn("version", pqt.TypeIntegerBig(), pqt.WithNotNull(), pqt.WithDefault("version+1", pqt.EventUpdate)

it will generate the following code in SELECT ... ON CONFLICT ... DO UPDATE SET ...:

INSERT INTO tablename (value, version) VALUES ('data', 0) 
ON CONFLICT (id) DO UPDATE SET value='data', version=version+1
RETURNING data, version

which will cause an error column reference "version" is ambiguous

Suggestion
Add table alias so it produce the code like

INSERT INTO tablename AS alias ... alias.version=version+1

Exclusion constraint support

Reference:
https://www.postgresql.org/docs/9.0/static/ddl-constraints.html
https://www.postgresql.org/docs/9.0/static/sql-createtable.html#SQL-CREATETABLE-EXCLUDE

Extend find method with recursive join statement.

Right now, with schema like A 1-n B 1-n C. Joining from C to A through B is not possible. So expression like:

filter := &model.CFindExpr{
            Offset:  req.Offset,
            Limit:   req.Limit,
            OrderBy: []model.RowOrder{model.RowOrder{Name: "id"}},
            JoinB: &model.BJoin{
                Fetch: true,
                Kind:  model.JoinInner,
                JoinA: &model.AJoin{
                    Fetch: true,
                    Kind:  model.JoinInner,
                },
            },
        }

will not fetch object A.