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

Referenced POJOs are not stored during save [moved] #116

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

Referenced POJOs are not stored during save [moved] #116

lvca opened this issue Dec 10, 2012 · 0 comments

Comments

@lvca
Copy link
Member

lvca commented Dec 10, 2012

This is Issue 116 moved from a Google Code project.
Added by 2010-09-19T11:23:30.000Z by jani.laa...@gmail.com.
Please review that bug for more context and additional comments, but update this bug.
Closed (Fixed).

Original labels: Type-Defect, Priority-High, v0.9.23

Original description

<b>What steps will reproduce the problem?</b>
1. Create Person, Company and Address POJOs. Person refers to Company and Company refers to Address.
2. save Person
3. Person and Company instances are stored to the database

<b>What is the expected output? What do you see instead?</b>
Person, Company AND Address instances should have been stored to the database

Or have I misunderstood so called cascading in OrientDB?
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