2
45%
master: 45%

Ran 10 May 2018 02:58PM UTC

Files 93

Run time 4s

Badge

Embed ▾

Committed 10 May 2018 02:36PM UTC coverage: 48.169% (+1.5%) from 46.663%

Job # 4836.2

Build Type

push

travis-ci

Committed by

tomka

Commit Message

Import management command: fix ID mapping of users and treenode parents

The introduction of statement level triggers for the skeleton summary
tables require a consistent treenode and class instance state after each
`mport statement. A consistent state means all referenced foreign keys
are available in the database. We currently use Django's deserialization
infrastructure, which relies heavily on the ORM. Therefore, importing
treenodes has gotten a tad more complicated. First, everything is
imported in a reasonable order by first storing semantic data like class
instances and only then moving on to spatial data. This allows skeletons
referenced by a treenode to be already present in the database. Second,
all treenodes are imported first without parent information, which
allows the statement level trigger to run and new IDs to be generated.
Once this is done a second pass will set the correct parent IDs.

Potentially more robust alternatives are: 1. disable the statement level
triggers during import and explicitly regenerate summaries after the
import completed and 2. create custom SQL to create treenodes in a
single statement (like SWC import) and have the statement level trigger
run only once.

Coverage Stats

7340 of 15238 relevant lines covered (48.17%)

0.48 hits per line

catmaid / CATMAID / 4836 / 2
45%
master: 45%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 4836.2

catmaid / CATMAID / 4836 / 2 45% master: 45%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 4836.2

catmaid / CATMAID / 4836 / 2
45%
master: 45%

README BADGES
x