11 Commits (ac12222556cae5a230332f2fe9808ef7c9bfaf5d)

Author	SHA1	Message	Date
ulferts	6cce947cbd	Chore/rename timestamps (#8765) ... * rename timestamps on time entry * add updated_at filter/order for time entries * rename on cost entries as well This will make handling in the cost query easier * adapt specs * linting * adapt project activity * update references to updated_on * remove outdated docs/code * global memberships are just memberships * rewire global membership creation/update/deletion * delete no longer required code and patches * move code to core * move specs to core * completely remove global roles in the form of a plugin * adapt specs * remove unused methods * migrate existing data * adapt membership representer to changed timestamps * global memberships available via API * implements created/update_at filters on memberships * update member on roles being added/removed * specify default value for created_at * fix project permission check and validation on members * adapt membership schema * adapt usage of sort by on members widget * support created/updated_on for api sort and filter * remove outdated model file * rename timestamps * allow specifying timestamp column for aaj * reload column information * further rename of created_on * include updated_at into journal creation * adapt document updated_at calculation * remove references to JournalVersion	4 years ago
ulferts	c546241459	extract into patch	5 years ago
ulferts	801811c6c0	avoid n+1 query for bcf issues on work package list	5 years ago
ulferts	0b15db3c9a	rename fixed_version to version	5 years ago
Henriette Dinger	bd7f4e4814	Update copyright notice	5 years ago
ulferts	0bc1fb094f	extract sharable code into module and superclass	5 years ago
ulferts	9c3206220b	remove mysql specific code throughout the application	6 years ago
Oliver Günther	ae8db4011a	Fix more deprecations	6 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