Disable nested set on digital_object table
|Assignee:||Mike Gale||% Done:|
|Category:||Performance / scalability|
|Target version:||Release 2.1.0|
|Google Code Legacy ID:||Tested version:|
Investigate if actively keeping a nested set is even needed on digital_object. If not, it's a free optimization :)
#5 Updated by Jessica Bushey about 8 years ago
- Status changed from QA/Review to Verified
I tested using numerous JPEGs, PDFs and MOVs.
I linked URLs, single digital objects and multiple digital objects.
I created fonds-level and series-level and item-level descriptions and attached digital objects.
I moved item-level descriptions.
I deleted series with numerous children and digital objects (VERY FAST)!
I created relationships.
I changed draft and published status.
I viewed browse digital objects page.
I added access points and authority records.
And I made sure everything worked properly in the cover flow viewer depending upon the number of images, the level of description etc..