Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
C
caosdb-server
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container registry
Model registry
Operate
Environments
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
GitLab community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
caosdb
Software
caosdb-server
Merge requests
!41
REL: update changelog, bump version of pom.xml, update DEPENDENCIES
Code
Review changes
Check out branch
Open in Workspace
Download
Patches
Plain diff
Expand sidebar
Merged
REL: update changelog, bump version of pom.xml, update DEPENDENCIES
release-v0.5.0
into
main
Overview
0
Commits
58
Pipelines
2
Changes
1
Merged
Timm Fitschen
requested to merge
release-v0.5.0
into
main
3 years ago
Overview
0
Commits
58
Pipelines
2
Changes
1
0
0
Merge request reports
Viewing commit
e2320592
Prev
Next
Show latest version
1 file
+
12
−
16
Inline
Compare changes
Side-by-side
Inline
Show whitespace changes
Show one file at a time
Verified
e2320592
STY: formatting
· e2320592
Timm Fitschen
authored
4 years ago
src/main/java/org/caosdb/server/entity/StatementStatus.java
+
12
−
16
View file @ e2320592
Edit in single-file editor
Open in Web IDE
Show full file
@@ -25,22 +25,18 @@ package org.caosdb.server.entity;
/**
* The statement status has two purposes:
*
* <p> 1. Storing the importance of an entity (any of ``OBLIGATORY``,
* ``RECOMMENDED``, ``SUGGESTED``, or ``FIX``). ``OBLIGATORY``,
* ``RECOMMENDED``, and ``SUGGESTED`` specify whether this Entity
* must, should or may be present, and whether the server will throw
* an error, a warning or nothing, respectively, if it is missing. The
* importance is also used to specify the level of inheritance whereby
* ``FIX`` means that the entity is never inherited. See <a
* href="../../../../../specification/RecordType.html">the
* documentation of RecordTypes</a> for more information.
*
* <p> 2. Marking an entity as a ``REPLACEMENT`` which is needed for
* flat representation of deeply nested properties. This constant is
* only used for internal processes and has no meaning in the
* API. That is also the reason why this enum is not called
* "Importance". Apart from that, in most cases its meaning is
* identical to the importance of an entity.
* <p>1. Storing the importance of an entity (any of ``OBLIGATORY``, ``RECOMMENDED``, ``SUGGESTED``,
* or ``FIX``). ``OBLIGATORY``, ``RECOMMENDED``, and ``SUGGESTED`` specify whether this Entity must,
* should or may be present, and whether the server will throw an error, a warning or nothing,
* respectively, if it is missing. The importance is also used to specify the level of inheritance
* whereby ``FIX`` means that the entity is never inherited. See <a
* href="../../../../../specification/RecordType.html">the documentation of RecordTypes</a> for more
* information.
*
* <p>2. Marking an entity as a ``REPLACEMENT`` which is needed for flat representation of deeply
* nested properties. This constant is only used for internal processes and has no meaning in the
* API. That is also the reason why this enum is not called "Importance". Apart from that, in most
* cases its meaning is identical to the importance of an entity.
*
* @author Timm Fitschen (t.fitschen@indiscale.com)
*/
Loading