Details
-
Task
-
Status: Closed
-
Major
-
Resolution: Fixed
-
3.0M6
-
None
Description
It should be beneficial to push entity type resolution down to the ResultSet processing stage (instead of doing it at the object resolution stage downstream). This way we can optimize inheritance queries to read only needed columns from the wide result set. Looks like this strategy is also applicable for the DataRow queries that do not resolve objects at the end, but still have an ObjEntity root.
Another reason to resolve inheritance close to the JDBC level, is to ensure the correct Java types of values. There is a hack (DataRowPostProcessor) that sort of handles it now, but it would be nice to steamline this processing.
This potentially obsoletes CAY-1136 (or at least makes it less of a priority).
Attachments
Issue Links
- is related to
-
CAY-795 Horizontal inheritance
- Open