|
||||||||||
PREV LETTER NEXT LETTER | FRAMES NO FRAMES |
predicate
, value
rr_attr_name { "," rr_attr_name }
columnName { "," columnName }
prefix columnName { "," prefix columnName }
prefix columnName { "," prefix columnName }
columnName { "," columnName }
columnName { "," columnName }
prefix columnName { "," prefix columnName }
prefix columnName { "," prefix columnName }
obj
.
initialConnections
target
object
this
object to target
fragementClass
; tuple deletion on
Fragmentation Relation leads to tuple deletion in Fragment Class (where
FR<> parameters match FC<> parameters)
fragmentClass
and uses fragmentClass
as trigger target; fragmentClass
must not bee Root Fragment
Class.
name
is used as root name for the created fragment class;
using a different value as the root name of its fragment base class will
cause errors.
fragmentClass
.
If the Derived Fragment Class is defined upon unfragmented Fragment Base
Class, only one trigger is to be created which is defined on the
Fragmentation Relation of its Derivation Base Class.
Otherwise trigger 1 is defined upon the Fragmentation Relation of its
Fragment Base Class, and trigger 2 is defined on the Fragmentation Relation
of its Derivation Base Class.
fragmentBaseClass
and derivation base Fragment
Class derivationBaseClass
.
fc_rootName
and
fc_paramNames
) based upon Fragment Base Class (designated by
bfc_rootName
and bfc_paramNames
).
fragmentBaseClass
to fragmentClass
, Trigger 2
triggers from derivedFragmentClass
to fragmentClass
;
Trigger 2 is seperated into before and after trigger to evade Mutating Table
problems; both triggers propagate tuple deleting/insertion/update to its
trigger target;
foundationFragmentClass
with a list of Fragment Classes
fragmentClasses
mapped.
"RP_" fr_rootName "_" rp_name
with the columns
label
and predicate
.
fragmentClass
.
fragmentClass
as base
Fragment Class, introducing the new parameter parameter
to
the Fragmentation.
fc_rootName
and
fc_paramNames
) based upon Fragment Base Class (designated
by bfc_rootName
and bfc_paramNames
).
fragmentClass
and uses fragmentClass
as trigger target; fragmentClass
must not bee Root Fragment
Class
fc_shortName
(parameter is held synchronous).
vbpParam
defined upon
Root Fragment Class designated by fc_rootName
and
fc_paramNames = null
by creating a table in database named
"RV_" fr_rootName "_" vbpParam
with the column
vpbParam
;
syncPolicy
specifies the synchronization between the column
of Root Fragment Class which is used as source for Value Parameter and its
Value Parameter relation (RV<>)
"synchronized
" creates a trigger which keeps the FC<>
parameter column and the RV<> parameter column synchronized; the RV<>
column contains exactly the same parameters as its source FC<>;
FC<> grows => RV<> grows; FC<> shrinks => RV<> shrinks
"expansive
" creates a trigger which forwards parameter
insertions to its RV<> relation;
FC<> grows => RV<> grows; FC<> shrinks => RV<> unchanged
"none
" no trigger created
vbpParam
defined upon
Root Fragment Class
designated by fc_rootName
and fc_paramNames = null
;
the Value Parameter relation is not generated from the Root Fragment Class,
it is mapped to an existing relation;
|
||||||||||
PREV LETTER NEXT LETTER | FRAMES NO FRAMES |