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
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
caosdb
Software
caosdb-server
Commits
e2320592
Verified
Commit
e2320592
authored
3 years ago
by
Timm Fitschen
Browse files
Options
Downloads
Patches
Plain Diff
STY: formatting
parent
24bffcc8
No related branches found
No related tags found
1 merge request
!41
REL: update changelog, bump version of pom.xml, update DEPENDENCIES
Pipeline
#9415
passed
3 years ago
Stage: setup
Stage: test
Stage: deploy
Changes
1
Pipelines
2
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
src/main/java/org/caosdb/server/entity/StatementStatus.java
+12
-16
12 additions, 16 deletions
src/main/java/org/caosdb/server/entity/StatementStatus.java
with
12 additions
and
16 deletions
src/main/java/org/caosdb/server/entity/StatementStatus.java
+
12
−
16
View file @
e2320592
...
@@ -25,22 +25,18 @@ package org.caosdb.server.entity;
...
@@ -25,22 +25,18 @@ package org.caosdb.server.entity;
/**
/**
* The statement status has two purposes:
* The statement status has two purposes:
*
*
* <p> 1. Storing the importance of an entity (any of ``OBLIGATORY``,
* <p>1. Storing the importance of an entity (any of ``OBLIGATORY``, ``RECOMMENDED``, ``SUGGESTED``,
* ``RECOMMENDED``, ``SUGGESTED``, or ``FIX``). ``OBLIGATORY``,
* or ``FIX``). ``OBLIGATORY``, ``RECOMMENDED``, and ``SUGGESTED`` specify whether this Entity must,
* ``RECOMMENDED``, and ``SUGGESTED`` specify whether this Entity
* should or may be present, and whether the server will throw an error, a warning or nothing,
* must, should or may be present, and whether the server will throw
* respectively, if it is missing. The importance is also used to specify the level of inheritance
* an error, a warning or nothing, respectively, if it is missing. The
* whereby ``FIX`` means that the entity is never inherited. See <a
* importance is also used to specify the level of inheritance whereby
* href="../../../../../specification/RecordType.html">the documentation of RecordTypes</a> for more
* ``FIX`` means that the entity is never inherited. See <a
* information.
* 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
* <p> 2. Marking an entity as a ``REPLACEMENT`` which is needed for
* API. That is also the reason why this enum is not called "Importance". Apart from that, in most
* flat representation of deeply nested properties. This constant is
* cases its meaning is identical to the importance of an entity.
* 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)
* @author Timm Fitschen (t.fitschen@indiscale.com)
*/
*/
...
...
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