4 Commits (cbcc4627f5c755a3d02526251332edb7ee904725)

Author	SHA1	Message	Date
Henriette Dinger	bd7f4e4814	Update copyright notice	5 years ago
Oliver Günther	3a69c1a6d8	[28452] Avoid adding a CF multiple times to eager loaded WPs ... If there is a custom field that is for_all, and it occurs multiple times in the custom_fields_projects join table, it will be added multiple times to the work packages availabe CFs. https://community.openproject.com/wp/28452	6 years ago
Oliver Günther	8438848838	[28435] Fix custom field with is_for_all eager loading ... When a custom field is `is_for_all`, and in the join table from custom fields to projects, there exist a value to project A (e.g., before the CF was marked is_for_all in the first place): Lookups to the work packages in Project B with eager loading will result in this custom field missing, because the `LEFT OUTER JOIN` in usages have already mapped it to Project A. https://community.openproject.com/wp/28435	6 years ago
Jens Ulferts	d04b86da9c	introduce custom eager loading for work package list ... Reduces the amount of AR models instantiated when handing wp#index requests by: * Calculating part of the checksum for caching in the db. This is done by using the id and the updated_at/on field of associated models whose representation is cached in the wp representer. * Reusing instantiated models for multiple associations. e.g instances of Project are used in various places (the work package itself, it's ancestors and children). Instead of using Rails' eager loading which would instantiate a project potentially once for every association path, the code now assigns the same instance to all those associations. Additionally, the commit streamlines the creation of custom field injected representers. Now only one class is created for all work packages when before it would be one class for every uniq set of custom fields. On top of that, the class can be reused if the set of custom fields does not change.	7 years ago