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

ReflectionSaveStatementGenerator:generateSaveOrUpdate #109

Open
JoniDS opened this issue May 5, 2016 · 0 comments
Open

ReflectionSaveStatementGenerator:generateSaveOrUpdate #109

JoniDS opened this issue May 5, 2016 · 0 comments

Comments

@JoniDS
Copy link

JoniDS commented May 5, 2016

When we have a structure Element->ElementChild->OtherChild(n) some records are not stored in the database and some references between the child(n) and the parent child are not created.
This will lead to some OtherChild in database without any link the the Element that owns them (they won't be deleted when we delete Element).

I've traced it to this code block (ReflectionSaveStatementGenerator:79):

if (contains(rushObjects, rush)) {
// Exit if object is referenced by child
//return;
}

The objects that aren't stored are the ones that enter this condition.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant