Changes between Version 26 and Version 27 of S3/S3Model/ComponentResources


Ignore:
Timestamp:
01/09/13 11:11:29 (9 years ago)
Author:
Dominic König
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • S3/S3Model/ComponentResources

    v26 v27  
    1313Each of these relationships can be represented by a join between the respective tables.
    1414
    15 The "Component Resource" extension provides the functionality to pre-configure and re-use these joins as pseudo-attributes ("components") of the master entity.
     15The "Component Resource" extension provides the functionality to pre-configure and re-use these joins as pseudo-attributes ("components") of the master entity, thereby replacing the joins by simple identifiers (aliases) which can be used to construct queries, e.g. in URLs:
     16
     17{{{
     18    # Join "office": org_organisation <-- id/organisation_id --> org_office
     19
     20    /org/organisation/5/office
     21}}}
     22
     23or
     24
     25{{{
     26    # Join "contact": pr_person <-- pe_id/pe_id --> pr_contact
     27
     28    /pr/person?contact.contact_method=EMAIL&contact.value=user@example.com
     29}}}
     30
     31The "Component Resource" extension is one of the fundamental RAD concepts of the S3 framework. Besides simplified construction of queries, views and self-processing forms it is also one of the fundamental premises for the implicit constraints in S3XML which simplify the mapping and transformation from and to other data models using XSLT.
    1632
    1733The following diagram describes the joins which are currently supported:
     
    1935[[Image(ComponentTypes.png)]]
    2036
     37Note that, for efficiency reasons, "components" can not be nested in queries.
    2138== Link-Table Components ==
    2239