examples:builder:belongsto_relation

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
examples:builder:belongsto_relation [2021/03/28 21:50]
pdsci-admin [Step 7: Add related fields to form and list] 		examples:builder:belongsto_relation [2021/04/11 19:27] (current)
pdsci-admin [The belongsTo relation]
Line 9: Line 9:
   * Required: a //**parent** table// and a //**child** table//    * Required: a //**parent** table// and a //**child** table// 
   * Create a model for the child table with list and form   * Create a model for the child table with list and form
-  * Add a field named: //[childModelName]// **to the parent table**+  * Add a field named: //[childModelName]_id// **to the parent table**
   * Extend **the parent controller** with relation behaviour   * Extend **the parent controller** with relation behaviour
   * Extend **the parent model** with the desired relation definition (//hasOne//)   * Extend **the parent model** with the desired relation definition (//hasOne//)
Line 132: Line 132:
 \\ \\
 Anyhow, if the //Record finder// is the preferred choice, the most important thing to define ist the //List configuration// (see the property box at the right in the picture below). Here a reference to the list view of the child model is required. In the library this is //$/pds/library/models/agegroup/columns.yaml//.\\ Anyhow, if the //Record finder// is the preferred choice, the most important thing to define ist the //List configuration// (see the property box at the right in the picture below). Here a reference to the list view of the child model is required. In the library this is //$/pds/library/models/agegroup/columns.yaml//.\\
-If for some reason the definition of the child list view is not suitable for the //Record finder// - for example if there are too many columns defined that are not of essence for the selection of a related record - another list view can be defined in the child model, holding only the columns needed. Let's call this view //columns_finder.yaml// then the reference has to be //$/pds/library/models/agegroup/columns_finder.yaml//+If for some reason the definition of the child list view is not suitable for the //Record finder// - for example if there are too many columns defined that are not of essence for the selection of a related record - another list view can be defined in the child model. For example to hold only the columns needed. Let's call this additional view //columns_finder.yaml//. Then the reference has to be //$/pds/library/models/agegroup/columns_finder.yaml//
 \\ \\
 \\ \\