diff options
authorBoris Kolpackov <>2015-02-04 17:23:54 +0200
committerBoris Kolpackov <>2015-02-04 17:23:54 +0200
commitd6bf93ae12d0a8cffcdb405392921583b420d8b4 (patch)
parent99cb130912baa9bf068c8b05bc99e86c542e115d (diff)
Implement object loading views
See section 10.2 in the manual for details.
-rw-r--r--reference/feature/view/object-loading (renamed from feature/view/object-loading)4
1 files changed, 2 insertions, 2 deletions
diff --git a/feature/view/object-loading b/reference/feature/view/object-loading
index 8ecabb2..95014e5 100644
--- a/feature/view/object-loading
+++ b/reference/feature/view/object-loading
@@ -1,4 +1,4 @@
-! Object loading views [2.4.0]
++ Object loading views
- The joined object can be joined just to be used in the query condition or
to load the data. How to distinguish the two cases and what should be the
@@ -18,7 +18,7 @@
a single SELECT) or it was JOIN'ed only for the query condition.
Since this is a performance feature, the defaul should probably
not to load. The mechanism used to specify this should probably
- also be used to specify whether to SELECT FOR UPDATE joined objacts.
+ also be used to specify whether to SELECT FOR UPDATE joined objects.
- Support both object pointer and direct member as an object (similar
to the load() signature). Might have to rely on delay loading. E.g.,