Goals

• streamlining of automated compilation process
• simplification of development compilation process
• minimizing dependence on build-helper-java parent pom

condense all possible source requirements into 1 pom-project

ROGM is missing any and all Tutorials and Guides that teach new users how to use and implement it.

• reloading for Nodes/Relation => load Node from Database and overwrite all current data of that Node/Relation
• unloading for Nodes/Relations=> save and remove from buffer

Todo

• update ci system (server architecture changed!)
• merge dependabot changes
• integrate upstream bugfix for utils-scanner

Goal
The goal is to officially complete what has started a long time ago in several unnoticed feature branches:
To restructure and modularize the Core of the Entity Management System hidden in the PatternStorage class to be able to modify and continue supporting it in the future.

This rework also includes that all of ROGM is compiled, tested and deployed unsing automated tests through Jenkins by utalising Maven, JUnit5 and Docker.

History

History of progress hidden in background changes / feature branches

Modularisation 14195e0

EntityReloading bcfe2c2

primary Stage of Rework 9b66c4f

PackageScanner af11ee6

introduced Jenkins & Docker b5fb4e7

propper test-artifact abe0d45

JUnit5 31c8af6

Tests by Group (system/db-neo4j) 202fc0e

2.0 deployed to master d4c687b

Issue

Maven Management buried the defined scopes of dependencies during dependency-management import

Solution

We will publish binary compatible source code with the next patch version

condense all possible requirements into 1 pom-project

Goal
Classes with the @NodeEntity or @RelationshipEntity may follow the Decorator Pattern, the decorated object must be annotated with @Decorated. Decorator-Classes may decorate other Decorator-Classes. All variables defined in Decorator-Classes will get saved in the same database object as the decorated entity.

ROGM is missing any and all In-Code Documentations that could help Open-Source Contributers develop Database-Modules

Incomplete Load-Filter (Load-Query) causes the Database to delete Relations.

IFilter customQuery = INodeFilter with only a select number of possible relations;

Object loadedObject = session.load(customQuery);
=> loads the Object as COMPLETE and stores it in the Buffer

session.save(loadedObject);
=> saves the buffered Object & deletes all outdated/unbuffered Relations since the Object is marked as COMPLETE

Database Diff.:
all Relations related to loadedObject & not explicitly defined in customQuery are deleted!

Module: MongoDB & Language: MQL (MongoDB Query Language)

Maven Modules:

<!-- Language: MQL (MongoDB Query Language) -->
<dependency>
  <groupId>net.runeduniverse.libs.rogm.lang</groupId>
  <artifactId>mql</artifactId>
  <version>2.0.1</version>
</dependency>

<!-- Module: MongoDB -->
<dependency>
  <groupId>net.runeduniverse.libs.rogm.modules</groupId>
  <artifactId>mongodb</artifactId>
  <version>2.0.1</version>
</dependency>

API: Expansion of Database Modules

Target Release

• Version: 2.2.X

API Packages

Core Extensions

Module: MariaDB & Language: SQL (Structured Query Language : Dialect MariaDB)

<!-- Language: SQL (Structured Query Language : Dialect MariaDB) -->
<dependency>
  <groupId>net.runeduniverse.libs.rogm.lang</groupId>
  <artifactId>sql-mariadb</artifactId>
  <version>2.1.1</version>
</dependency>

<!-- Module: MariaDB -->
<dependency>
  <groupId>net.runeduniverse.libs.rogm.modules</groupId>
  <artifactId>mariadb</artifactId>
  <version>2.1.1</version>
</dependency>

IDs don't get returned correctly and are overwritten on insert by SET a = {...}
(Buffer changes recommended to around saving the node id and the object id as different variables)

Problem

ROGM is designed and was in the past (version: 1.1.11) able to link multiple relations to a single node.

At the current time(version: 2.1.2 Latest) ROGM only indexes the first occurrence of a field annotated with @Relationship

implement cascading loading of Nodes/Relations

Buffer

internally saves the relation pointer to the loaded objects and speeds up repeated querys

Order Objects by:

• Node/Relation
• Database ID
• Object ID (defined with @Id and can be synced with Database ID)
• Class/Labels(Type)

Node/Relation gets loaded/searched from Users

• search according to the class and their children (take child before loading base Class from Database)

Node/Relation gets loaded/searched from Database (on loading)

• search and parse according to the label of the Node

• add delete for Nodes and Relations
• also enforce deletion of relations when saving Relation lists in Nodes

Goal
Include ability to reload entities where the entity's reference must stay the same!
Reloaded entities may define a @PostReload method.