Project

General

Profile

Feature #17271

Feature #17269: Use subrun ranges instead of individual subruns in metadata

Add database support for subrun ranges

Added by Robert Illingworth over 2 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
07/25/2017
Due date:
% Done:

0%

Estimated time:
Duration:

Description

Add database support for subrun ranges. The simplest method would be to add a nullable max_subrun value, although this would complicate queries. Changing subruns to a Postgres range type would be more efficient, but more disruptive.

In most cases subruns aren't used in complex queries (or queried much at all), so extra complexity probably isn't an issue.



Also available in: Atom PDF