| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
When `domagi extract` is given a path range, it may select
discontinuous fragments of other paths. These fragments must be output
as separate paths, not erroneously merged together.
|
|
|
|
|
|
|
|
In domagi extract, order path_segment by the output start and end
coordinates, not the input start and end coordinates. We achieve this
by renaming the output coordinates "start" and "end" respectively.
|
|
|
|
|
|
|
|
|
|
|
|
We also fix the test to pass in a string rather than a Path.
|
|
|
|
|
|
It's nice to have the $1, $2 and $3 line up in that order.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The threads variable name can be derived automatically from the
--threads option name.
|
|
|
|
This eases testing of domagi during development.
|
|
|
|
|
|
|
|
We need to initialize the schema in the output database so that we get
things like views.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This was completed in 185b459cc11a2e8661817f2750d98f9051541761.
|
|
|
|
The SQL query was completely wrong. It was most likely meant to work
with an earlier version of the schema.
|
|
|
|
|
|
|
|
|
