Skip to content
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

Support the JPA annotation for the Object Database interface [moved] #102

Closed
lvca opened this issue Dec 10, 2012 · 0 comments
Closed

Support the JPA annotation for the Object Database interface [moved] #102

lvca opened this issue Dec 10, 2012 · 0 comments

Comments

@lvca
Copy link
Member

lvca commented Dec 10, 2012

This is Issue 102 moved from a Google Code project.
Added by 2010-08-22T15:52:56.000Z by l.garu...@gmail.com.
Please review that bug for more context and additional comments, but update this bug.
Closed (Fixed).

Original labels: Type-Enhancement, Priority-Low, v0.9.25

Original description

OrientDB could support the JPA annotations:

- @Entity, to determine which classes are persistent entities
- @Embedded, tells that is an embedded type (1, collection or map)
- @Id, to let to a domain field to contain the @rid content
- @Version, to let to a domain field to contain the @version content
- @UniqueConstraint, to define a unique index against that property. OrientDB doesn't support (yet) a unique constraint for multiple fields
- @Transient, to mark transient fields
- @Basic(fetch = FetchType.LAZY), to determine the fetch mode
- @Access(AcessType.PROPERTY), to access to the field directly without calling the getter/setter
- @OneToOne, @ManyToOne, @OneToMany or @ManyToMany to declare relationships
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant