-
Notifications
You must be signed in to change notification settings - Fork 95
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide a JPA-based ORM implementation #172
Comments
Other options for providing an ORM implementation could be the following: If this is something that's going to be considered, a mention of an approximate timeframe expectation would be quite appreciated. |
@haqer1 Thanks for your feedback. We're internally discussing regularly about supporting different ORMs. So far we provide support for Spring Data. Other may follow but I can neither guarantee it nor give it an appointment. |
Considering various possibilities, I've made the subject line a bit more specific. P.S. Perhaps other possibilities could be considered separately. For instance, a JDO-based ORM implementation as part of, e.g., |
Nice, we in Eclipse JNoSQL are working to make support to Aranbodb also: |
@otaviojava Is your driver support production ready or still under development? |
The project still in development, however, both the API is pretty stable, and we seek to success case. We already have some, yet, none with ArangoDB. I wrote an article about it: |
The following might influence some people's choice of which NoSQL approach they choose:
https://wiki.eclipse.org/EclipseLink/Examples/JPA/NoSQL
Some kind of ORM implementation or contribution to an ORM framework for ArangoDB would make it much more appealing.
P.S. Since they've managed to do this for MongoDB, which doesn't have a QL, it should be very much doable for ArangoDB.
The text was updated successfully, but these errors were encountered: