persist N records with the manager and save them as flushing about orientdb-odm HOT 4 OPEN

Hey,

Are there any plans on this?

I have looked through the code (admittedly not in great detail) and saw some oddities. For example the Mapper looks like a mixture of hydration / proxy factory. Also as I have seen the Manager is more of a proof of concept thing now initiating a proxy class and all.

I didn't really get what's the purpose of Collection and Value

I have a month or so that I could spend and would be interested in picking it up, but I'd like to know if there are any plans for how you wish to proceed and how open are you (the project) to refactoring?

/cc @odino

from orientdb-odm.

Hi @mitom,
the main idea was to build a data mapper very close to the ORM or better ODM ( like the one for mongo ). I started working on the "persistence" branch ... but now is 2 years ago :(

The bad news is that i think is an hard job ... the good one is that you can see how the other projects did.

But, wow, you have a month to work on this task ... is amazing.
@odino can we get in touch to give support ( ... in planning )

from orientdb-odm.

Hi @davidino,

I am going to open separate issues for the different parts so it's easier to track their process and discussions. I'll also try to create WIP PRs so you guys can give feedback if things are going in the right direction.

My plan is to take as much as possible from doctrine common, given how this is a doctrine project now. I hope orientdb being a graph database won't have many consequences on the lower levels, rather in providing high level functions.

I think the first dependency of this will be #183

from orientdb-odm.

no problem for me in terms of refactoring some of the internal APIs but at the same time keep in mind that some things are fundamentally different (being a graphdb) compared to the usual ORM stuff :)

from orientdb-odm.