1
69%
master: 97%

Ran 22 Oct 2015 04:29PM UTC

Files 87

Run time 8s

Badge

Embed ▾

Committed 22 Oct 2015 04:15PM UTC coverage: 68.735%. First build

Job # 8755.1

Build Type

push

travis-ci

Committed by

nickstenning

Commit Message

Set up a constraint naming convention for sqlalchemy

In order to be able to add and remove constraints using alembic, they
must be named. Luckily for us PostgreSQL does actually have a reasonably
sensible constraint naming convention, but enforcing this in sqlalchemy
allows us to know what constraints are called without referring to the
database in question.

In addition, the default PostgreSQL naming convention suffers from
clashes: an FK constraint on the column "id" on a join table called
"foo_bar" will be named "foo_bar_id_fkey", which is the same name as
would be given to an FK constraint on the "bar_id" column on table
"foo". The naming convention chosen here doesn't suffer from the same
problem (presuming that you never use "__" in column names).

This commit includes a migration to update existing constraints to the
new naming convention.

Run Details

2515 of 3659 relevant lines covered (68.73%)

0.69 hits per line

hypothesis / h / 8755 / 1
69%
master: 97%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 8755.1

hypothesis / h / 8755 / 1 69% master: 97%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 8755.1

hypothesis / h / 8755 / 1
69%
master: 97%

README BADGES
x