9 Commits (8fe9a81387a86d14d8196bf0e7be2cb820b3fcc5)

Author	SHA1	Message	Date
ulferts	8c732b9a42	Fix/parent depth first sorting (#6133) ... * maintain hierarchy path for performant sorting * by default - only sort by parent Parent sorting is exclusive as the sorting used is depth first. Because of that, the id of the work package is always part of the parent order criteria. By that, all other properties of the work package become irrelevant. [ci skip]	7 years ago
ulferts	a28ec25957	Fix/parent sorting missing elements (#6118) ... * Revert "remove unused sortable join (#6099)" This reverts commit c1be19a6da. * prevent descendant wps to not be present in filter result on parent sort On sorting by parent, we need to join the query with a subselect that returns only the topmost hierarchy relation (i.e. the relation that has the highest hierarchy value) per work package. Otherwise, if more than one row is returned per wp for the subquery, the work package is also counted multiple times against the provided limit which leads to less work packages being returned than expected. [ci skip]	7 years ago
ulferts	c1be19a6da	remove unused sortable join (#6099) ... [ci skip]	7 years ago
ulferts	587c3d6d40	fix poor mysql performance on sorting by parent (#6059) ... [ci skip]	7 years ago
ulferts	7d5616119f	replace dynamic AR method by static string (#6049) ... In cases where the filters are loaded before the migrations have run, the relations table might not exist. [ci skip]	7 years ago
Oliver Günther	0d55bc0308	[26675] Remove implicit ID sorting on parent sort (#6039) ... * [26675] Remove implicit ID sorting on parent sort https://community.openproject.com/wp/26675 * parent sort -> breadth first sort, top down [ci skip]	7 years ago
Jens Ulferts	6fdd122534	merge wp tree and relations into typed_dag ... Instead of having the tree/hierarchy information for work packages and the relations between the work packages separated into two tables all the information is now stored in the relations table. To support this, the typed_dag plugin is used. Notable changes: * relations_to and relations_from are swapped. relations_to has all relations that point to another work package (from_id = work_package.id) and relations_from contains all relations that lead to the work package from another one (to_id = work_package.id). This change is merely in the code. The db information is left untouched. * For follows/precedes to_id and from_id are swapped in the db. Because of that, "follows" is now the canonical name instead of "precedes". This is done so that hierarchy relations and follows relations point into the same direction which allows to easily detect cyclic relationships that would lead to infinit scheduling. * the columns `root_id`, `lft`, `rgt` do no longer exist in the wp table. * the column `relation_type` does no longer exist in the relations table. * For every type of relation a column (integer) does now exist in the relations table (e.g. hierarchy, block, follow) * Separate associations exist for every type of relation into two directions. E.g. Work packages following the current one can be accessed via `work_package.precedes`	7 years ago
ulferts	ace7098eb3	add relations columns to query (#5606) ... * add relations columns to query * refactory query columns * rename QueryColumn to QueryColumn::Property QueryColumn is now only an abstract supertype [ci skip]	8 years ago