Changes between Version 17 and Version 18 of RESTController


Ignore:
Timestamp:
11/20/09 01:19:50 (12 years ago)
Author:
Dominic König
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • RESTController

    v17 v18  
    7070== Model ==
    7171
    72 Example for definition of a joined resource in the model:
     72Example for definition of a component table in the model:
    7373
    7474{{{
     
    9595where:
    9696
    97   - '''module''' is the name of the module in which the joined resource is defined (prefix)
    98   - '''resource''' is the name of the joined resource
    99   - '''multiple''' indicates whether this is a 1:N (True) or 1:1 (False) join, defaults to True
     97  - '''module''' is the name of the module in which the component is defined (prefix)
     98  - '''resource''' is the name of the component
     99  - '''multiple''' indicates whether this is a N:1 (True) or 1:1 (False) join, defaults to True
    100100  - '''joinby''' describes the join keys:
    101101    - pass a single field name for natural joins (same key field in both tables)
    102102    - pass a dictionary of ''tablename=fieldname'' pairs for primary/foreign key matching, in which:
    103103      - ''tablename'' is the name of the respective primary table
    104       - ''fieldname'' the name of the foreign key in the joined table that points to the ''id'' field in the primary table
     104      - ''fieldname'' the name of the foreign key in the component table that points to the ''id'' field in the primary table
    105105      - e.g. {{{joinby = dict(pr_person='person_id')}}}
    106   - '''fields''' is a list of the fields in the joined resource that shall appear in list views:
     106  - '''fields''' is a list of the fields in the component that shall appear in list views:
    107107    - if omitted or set to None, all readable fields will be included
    108108