From f5e457f5dee11cbd20fc3557f79d6e1f235fb89f Mon Sep 17 00:00:00 2001
From: Boris Kolpackov The name part is a potentially qualified persistent class
@@ -9960,12 +9961,16 @@ struct employee_employer
part gives this object an alias. If provided, the alias is used
in several contexts instead of the object's unqualified name. We
will discuss aliases further as we cover each of these contexts
- below. The optional join-condition part provides the
+ below. The optional join-type part specifies the way this
+ object is associated. It can be object(name
[= alias]
+ [join-type]
[: join-condition])
left
, right
,
+ full
, inner
, and cross
+ with left
being the default.
+ Finally, the optional join-condition part provides the
criteria which should be used to associate this object with any
of the previously associated objects or, as we will see in
Section 10.4, "Mixed Views", tables. Note that
while the first associated object can have an alias, it cannot
- have a join condition.
For each subsequent associated object the ODB compiler needs a join condition and there are several ways to specify @@ -10784,6 +10789,7 @@ struct employee_max_vacation
table("name"
[= "alias"]
+ [join-type]
[: join-condition])
The name part is a database table name. The optional
@@ -10791,12 +10797,16 @@ struct employee_max_vacation
alias must be used instead of the table whenever a reference
to a table is used. Contexts where such a reference may
be needed include the join condition (discussed below),
- column names, and query expressions. The optional join-condition
+ column names, and query expressions. The optional join-type
+ part specifies the way this table is associated. It can
+ be left
, right
, full
,
+ inner
, and cross
with left
+ being the default. Finally, the optional join-condition
part provides the criteria which should be used to associate this
table with any of the previously associated tables or, as we will see in
Section 10.4, "Mixed Views", objects. Note that
while the first associated table can have an alias, it cannot have
- a join condition.
Similar to object views, for each subsequent associated table the ODB compiler needs a join condition. However, unlike for object views, -- cgit v1.1