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

Timestamp:

01/09/13 11:11:29 (13 years ago)

Author:

Dominic König

Comment:

--

S3/S3Model/ComponentResources

@@ -13 +13 @@
 Each of these relationships can be represented by a join between the respective tables.
 
-The "Component Resource" extension provides the functionality to pre-configure and re-use these joins as pseudo-attributes ("components") of the master entity.
+The "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:
+
+{{{
+    # Join "office": org_organisation <-- id/organisation_id --> org_office
+
+    /org/organisation/5/office
+}}}
+
+or
+
+{{{
+    # Join "contact": pr_person <-- pe_id/pe_id --> pr_contact
+
+    /pr/person?contact.contact_method=EMAIL&contact.value=user@example.com
+}}}
+
+The "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.
 
 The following diagram describes the joins which are currently supported:
@@ -19 +35 @@
 [[Image(ComponentTypes.png)]]
 
+Note that, for efficiency reasons, "components" can not be nested in queries.
 == Link-Table Components ==