Changes between Version 17 and Version 18 of RESTController

Timestamp:

11/20/09 01:19:50 (15 years ago)

Author:

Dominic König

Comment:

--

RESTController

@@ -70 +70 @@
 == Model ==
 
-Example for definition of a joined resource in the model:
+Example for definition of a component table in the model:
 
 {{{
@@ -95 +95 @@
 where:
 
-  - '''module''' is the name of the module in which the joined resource is defined (prefix)
-  - '''resource''' is the name of the joined resource
-  - '''multiple''' indicates whether this is a 1:N (True) or 1:1 (False) join, defaults to True
+  - '''module''' is the name of the module in which the component is defined (prefix)
+  - '''resource''' is the name of the component
+  - '''multiple''' indicates whether this is a N:1 (True) or 1:1 (False) join, defaults to True
   - '''joinby''' describes the join keys:
     - pass a single field name for natural joins (same key field in both tables)
     - pass a dictionary of ''tablename=fieldname'' pairs for primary/foreign key matching, in which:
       - ''tablename'' is the name of the respective primary table
-      - ''fieldname'' the name of the foreign key in the joined table that points to the ''id'' field in the primary table
+      - ''fieldname'' the name of the foreign key in the component table that points to the ''id'' field in the primary table
       - e.g. {{{joinby = dict(pr_person='person_id')}}}
-  - '''fields''' is a list of the fields in the joined resource that shall appear in list views:
+  - '''fields''' is a list of the fields in the component that shall appear in list views:
     - if omitted or set to None, all readable fields will be included