Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
CaosDB Crawler
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
caosdb
Software
CaosDB Crawler
Commits
1d9d7db5
Commit
1d9d7db5
authored
3 years ago
by
Henrik tom Wörden
Browse files
Options
Downloads
Patches
Plain Diff
entity
parent
fb35bab5
No related branches found
Branches containing commit
No related tags found
Tags containing commit
1 merge request
!53
Release 0.1
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
concept.md
+18
-1
18 additions, 1 deletion
concept.md
with
18 additions
and
1 deletion
concept.md
+
18
−
1
View file @
1d9d7db5
...
...
@@ -61,11 +61,28 @@ identified. Suggestion: A unique query defines it.
Example: "FIND RECORD Fish WITH FishNumber=A AND WHICH IS REFERENCED BY B"
Note that the second part would be no usable condition with the old
identifiable concept.
The query must return 1 or 0 entities. If no entit
i
y is returned the respective
The query must return 1 or 0 entities. If no entity is returned the respective
object may be created and if one is returned it is the one we were looking for.
If more than one is returned, then there is a mistake in the definition or in
the data set.
## Entity Construction
In the simplest case an entity is constructed at a given node from its key
value pairs. However, the data for a given entity might be distributed over the
tree. Two different approaches are possible:
1.
During the construction of an entity at a given node also key value pairs
from other nodes are used. For example, key value pairs from parent nodes might
be made accessible. Or key value pairs might be accessed by providing the path
to them in the tree.
2.
Information is added to an entity at other nodes. The simplest case uses the
identifiable definition to add information. I.e. it is checked whether the
respective entity does already exist in the server, if not it is inserted and
then the information is added.
Additionally, it could be made possible to add information to entities that are
constructed in other nodes without the use of the identifiable. For example,
could it be allowed to add information to entities that were created at parent
nodes.
## Value computation
It is quite straight forward how to set a Property of a Record with a value
that is contained in the hierarchical structure. However, the example with the
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment