Skip to content
Snippets Groups Projects

FIX: if multiple updates for one entity exist, the retrieve would result in an...

Merged Alexander Schlemmer requested to merge f-reuse-yaml-doc into dev
1 file
+ 35
0
Compare changes
  • Side-by-side
  • Inline
+ 35
0
@@ -86,6 +86,41 @@ list of previously defined names of Properties and/or RecordTypes. Note that if
@@ -86,6 +86,41 @@ list of previously defined names of Properties and/or RecordTypes. Note that if
recommended_properties:
recommended_properties:
Author:
Author:
 
Reusing Properties
 
==================
 
 
Properties defined once (either as a property of a Record or as a separate Property) can be reused
 
later in the yaml file. That requires that after the first occurrence of the property, the
 
attributes have to be empty. Otherwise the reuse of the property would be conflicting with its
 
original definition.
 
 
Example:
 
--------
 
 
 
.. code-block:: yaml
 
 
Project:
 
obligatory_properties:
 
projectId:
 
datatype: INTEGER
 
description: 'UID of this project'
 
date:
 
datetype: DATETIME
 
description: Date of a project or an experiment
 
 
Experiment:
 
obligatory_properties:
 
experimentId:
 
datatype: INTEGER
 
description: 'UID of this experiment'
 
date: # no further attributes here, since property was defined above in 'Project'!
 
 
 
The above example defines two Records: Project and Experiment
 
The property ``date`` is defined upon its first occurrence as a property of ``Project``.
 
Later, the same property is also added to ``Experiment`` where no additional attributes are
 
allowed to specify.
Datatypes
Datatypes
=========
=========
Loading