Changes between Version 33 and Version 34 of S3/S3Model/SuperEntities

Timestamp:

04/01/14 12:12:17 (11 years ago)

Author:

Dominic König

Comment:

--

S3/S3Model/SuperEntities

@@ -96 +96 @@
 === Linking to a Super-Entity ===
 
-Both, instance tables as well as shared components need to be linked to the super-entity. This can be done by inserting a ''super-key'' field into the instance/component table which must have the same name as the primary key of the super-entity. You can use the {{{super_link()}}} function as a DRY method for this:
+Both, instance tables as well as shared components need to be linked to the super-entity. 
 
-{{{
+This can be done by inserting a ''super-key'' field into the instance/component table which must have the same name as the primary key of the super-entity. You can use the {{{super_link()}}} function to do this:
+
+{{{#!python
 tablename = "pr_presence"
 table = db.define_table(tablename,
@@ -108 +110 @@
 Note: {{{super_link}}} generates a {{{Field}}} instance - if you just need the name of the super-key field, you can use:
 
-{{{
+{{{#!python
 sk = s3db.super_key(db.pr_pentity) # returns the string "pe_id"
 }}}
+
+...or just type the field name (best option in models with lazy tables).
 === Updating a Super-Entity ===