6 Commits (047e972653a1af38e205c75aff735ee3eb7e2425)

Author	SHA1	Message	Date
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
Oliver Günther	cbb0d90fde	Use Rack::Test in all request specs	7 years ago
Oliver Günther	6ff79e0fd8	Fix flickering spec by not requiring explicit ID values ... If certain relation ids already existed, this spec will fail due to ordering of relations. Instead, check for the inserted relation id.	7 years ago
Oliver Günther	bcdedaff15	Avoid ordering issues in pg for relations filter	7 years ago
Oliver Günther	7cf11bb689	Update copyright notice	8 years ago
Markus Kahl	bc444a86ec	filters for relation API	8 years ago