Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
C
caosdb-mysqlbackend
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-mysqlbackend
Commits
5b22d1e5
Verified
Commit
5b22d1e5
authored
4 years ago
by
Timm Fitschen
Browse files
Options
Downloads
Patches
Plain Diff
DOC: CHANGELOG
parent
fff412fa
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
CHANGELOG.md
+32
-0
32 additions, 0 deletions
CHANGELOG.md
with
32 additions
and
0 deletions
CHANGELOG.md
+
32
−
0
View file @
5b22d1e5
...
...
@@ -10,8 +10,40 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
### Added ###
*
New
`feature_config`
table for storing configuration of features as key-value
pairs. Currently only used by the ENTITY_VERSIONING feature for switching
versioning on or off. Convenient function
`is_feature_config`
for checking
whether the
`feature_config`
table has a particular value.
*
New
`transactions`
table. This is necessary for the ENTITY_VERSIONING feature
and will replace the
`transaction_log`
table in the future.
*
ENTITY_VERSIONING (experimental)
Switch off this feature with
`DELETE FROM feature_config WHERE
_key="ENTITY_VERSIONING"`
and switch on with
`INSERT INTO feature_config
(_key, _value) VALUES ("ENTITY_VERSIONING", "ENABLED")`
This feature comes
with a lot of additions to the API. E.g.
*
New
`entity_version`
.
*
All
`*_data`
tables have a new twin, the
`archive_*_data`
table, where all
old versions of entities are stored. The
`*_data`
tables only contain the
data of the latest version.
*
Additional
`archive_isa`
for the history entities' parents.
*
Additional
`_iversion`
column for the
`reference_data`
table for storing
references to particular versions of an entity.
*
New
`setFileProperties`
and
`retrieveQueryTemplateDef`
procedures which reduce server code and lets the
backend decide which tables to use. Also, this is necessary for the
versioning, because this procedure behaves differently depending on the
ENTITY_VERSIONING feature being enabled or disabled.
*
Several functions and procedures for the interaction with the
`entity_version`
table and the
`transactions`
table. E.g.
`insert_single_child_version`
,
`delete_all_entity_versions`
,
`get_iversion`
,
`get_primary_parent_version`
,
`get_version_timestamp`
,
`get_head_version`
,
`get_head_relative`
,
`get_version_history`
.
The versions are tracked internally by the
`_iversion`
field which is an
integer and which should not be used outside of the backend.
### Changed ###
*
removed
`getFile`
procedure.
### Deprecated ###
*
Table
`transaction_log`
is deprecated. The functionality is being replaced by the
`transactions`
table.
...
...
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