Changes between Version 8 and Version 9 of RESTController
- Timestamp:
- 11/20/09 00:21:01 (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
RESTController
v8 v9 24 24 ''(This extends the single-table [wiki:BluePrintRESTImplementation REST Implementation])'' 25 25 26 A joined resource request is a request to a table ("joined resource" or "'''component'''") in dependency of a join to another table ("primary resource" or simply "'''resource'''"), e.g.:26 A '''joining request''' is a request to a table ('''component''') in dependency of a join to another table ('''resource'''), e.g.: 27 27 28 * the list of addresses (=component) of a person (=resource) .28 * the list of addresses (=component) of a person (=resource) 29 29 30 There are different ways how "Joined Resources" can be seen: 30 A resource and its components together represent a "Joined Resource". 31 31 32 - as subtables of database tables 33 - as structured properties of object classes 34 - as component classes within data compounds 32 There are different ways how such joined resources can be seen: 35 33 36 In this implementation, component resources can be joined 1:1 or N:1 to their primary resources, either by natural joins (same key field in both tables) or primary/foreign key matches, where the primary key is always the 'id' field in the primary table. 34 - as database tables with embedded subtables 35 - as data objects with structured properties 36 - as compound objects with component classes 37 38 In this implementation, component tables can be joined 1:1 or N:1 to their primary resources, either by natural joins (same key field in both tables) or primary/foreign key matches, where the primary key is always the 'id' field in the primary table. 37 39 38 40 == Model ==