Because it belongs to an archived project. Jira admins can restore projects from the archive.
Reuse association data loaded from the main entity when loading from Tuple
Description
Today the Tuple only represents the entity information and not the association information even if that data has been loaded by the native call.
It would be nice to offer that data (via a fake resultset) and let it be reused by the OgmLoader. This will require to create this fake resultset but also to properly handle collection / association persisters whose handling I removed initially from OgmLoader.
Is this true any longer? Now that we can attach the native representation to the entity entry, we e.g. already have the ids of referenced entities when loading a MongoDB document.
Emmanuel BernardFebruary 19, 2014 at 3:45 PM
I suspect this feature will be needed during our perf and unnecessary lookup checks.
Today the Tuple only represents the entity information and not the association information even if that data has been loaded by the native call.
It would be nice to offer that data (via a fake resultset) and let it be reused by the OgmLoader. This will require to create this fake resultset but also to properly handle collection / association persisters whose handling I removed initially from OgmLoader.