Check out this post: https://groups.google.com/forum/#!searchin/orient-database/object$20api$20deprecate/orient-database/9V4p1v_iZkg/qIaYQRuGhykJ
Luca states they will not deprecate it, but rather improve on a per-case basis. For our project we heavily use Object API and I made a whole bunch of bugfixes and a bit of improvements on the Object API and they were all accepted, except for one which will go into 2.2. Op maandag 15 juni 2015 14:20:11 UTC+2 schreef xvik: > > I join the question about the future of object api. > > According to the documentation: This API hasn't been improved since > OrientDB 1.5. Please consider using Document or Graph API by writing an > additional layer of mapping with your POJO. > > Can you assure that it would not be deprecated? > Can you assure that it would still be maintained in future releases? > Do you plan to improve object api in the future releases? > > I love object api and I bet on it as the simplest way to work with > orient from java. > Graph features work well with object api (usually I mix apis and it works > very well). > I just want to be sure that it won't disappear someday (and there is no > alternative for it) > > понедельник, 15 июня 2015 г., 18:05:30 UTC+6 пользователь Chaitanya Reddy > написал: >> >> Hi >> >> It looks like ObjectDb also pretty cool. Why is it 50% slower compared >> with DocumentDb? >> >> Thank you >> Chaitanya >> > -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
