Luigi Dell'Aquila

yep, this was the initial proposal and IMHO it's acceptable. I think @tglman has something in mind about lazy fetching...

Additional proposal, always related to the APIs, but this time about the DB. I'd like to add to ODatabase the following methods: ``` java public OClass createClass(String className, String... superclasses);...

I was waiting for this question ;-) Indexes are mainly related to classes, so IMHO it's OK to get a Class from the DB and use it to manipulate its...

Just pushed the first version of this multi-model API to develop branch

+1 Just a couple of notes about the RID representation with three numbers: - It's obvious, but I'll stress on this: with this approach RIDs will be reused and sequential...

IMHO this solution does not make much sense as long as we use varint to represent single parts of the RID

Hi @lag-linaro I think this PR is outdated, we reviewed all the docker images so now it should be architecture-agnostic If you have a chance, please double-check and let me...

Hi @odidev I'm afraid I don't get the point here... The new Docker images (see https://github.com/orientechnologies/orientdb-docker/tree/master/release) are already multi-arch and based on the new guidelines... Thanks Luigi

Hi @ghatwala The problem here is that alpine image is no longer supported by DockerHub (see https://github.com/docker-library/official-images/pull/6018 and https://github.com/docker-library/openjdk/pull/322) so I don't know if this PR makes much sense in...

Hi @bblonski Is this issue still valid? I checked the code but too many things have changed, so the patch from @ken-at-sri cannot be applied anymore Thanks Luigi